[Peek] Add support for previewing .ahk files as plaintext

[daverayment]

Summary of the Pull Request

This replaces the previous #34824 PR. That PR's feature to allow the previewing of arbitrary plaintext files is not available here and is covered by a separate issue.

This change allows for the previewing of AutoHotKey .ahk script files with the Monaco renderer in Peek (via the WebBrowserPreviewer).

PR Checklist

• Closes: PowerToys Peek support for AutoHotkey scripts #34483
• Communication: I've discussed this with core contributors already. If work hasn't been agreed, this work might be rejected
• Tests: Added/updated and all pass
• Localization: All end user facing strings can be localized
• Dev docs: Added/updated
• New binaries: Added on the required places
  • JSON for signing for new binaries
  • WXS for installer for new binaries and localization folder
  • YML for CI pipeline for new test projects
  • YML for signed pipeline
• Documentation updated: If checked, please file a pull request on our docs repo and link it here: #xxx

Detailed Description of the Pull Request / Additional comments

The .ahk file extension has been added to the relevant Monaco settings files, in a similar manner to the addition of .srt files previously.

A small fix was made to MonacoHelper.cs by placing a using for the JsonDocument instantiation there, as it was not Disposed previously.

Validation Steps Performed

• I used the current version of PowerToys to attempt to open .ahk files on my machine. I confirmed that the contents were not rendered and the UnsupportedFilePreview was used to show summary information only.
• I confirmed the .ahk files could be opened as plaintext with the updated build.
• I ran through my test folder, which contains a mix of image files, documents, text files and so on, confirming there were no issues created for other file types.

[daverayment]

I am currently looking into a bug with the exclusion code. Please hold off from reviewing for now. Thanks.

[daverayment]

@htcfreek @crutkas

Could I request some help here, please?

When you add a file extension for previewing with Monaco by editing 'monacoSpecialLanguages.js' and 'monaco_languages.json', PowerToys will create a shellex entry in the Registry for that extension on startup:

(With {D8034CFA-F34B-41FE-AD45-62FCBB52A6DA} here referring to the Monaco Preview Handler.)

This is fine for file extensions which don't already have preview handlers defined. However, it looks like PowerToys will overwrite any existing entry present for that extension, too. I've been trying to study the code which registers the Monaco types in the registry (in 'modulesRegistry.h' and 'registry.h'), and I've done some testing to confirm the behaviour, but my C++ isn't very strong and I may be mistaken. In any case, I could use some advice.

If this behaviour is correct, we can't add .csv to Monaco's supported list, as it would overwrite the existing Office-installed Excel previewer handler if someone had that installed. Also, is it intended that PowerToys overwrites any predefined handlers for the other file extensions, too? Shouldn't there be code in getMonacoPreviewHandlerChangeSet to add extensions with existing handlers to the ExtExclusions list?

I'm sorry if this is intended behaviour or I'm misunderstanding, but it seemed suspicious and I wanted to be sure.

[daverayment]

This issue seems to confirm that existing preview handler entries are being overwritten by PowerToys. Handlers installed by Office would be common examples, but there could be others.

[daverayment]

As discussed previously, I have removed .csv and .tsv support, and this PR now only adds .ahk support for Peek.

[htcfreek]

@daverayment
Can you update the linked issues, pr title and description please.

[daverayment]

@htcfreek Thanks for the reminder. Done.

[jaimecbernardo]

LGTM! Thank you for the contribution!