Validator for UXP is now available on VSCode Marketplace: Validator for UXP - Visual Studio Marketplace 
And open-sourced on GitHub: GitHub - jardicc/vscode-uxp-validator 
Please check it and let know your feedback. Also any info to improve rules is highly appreciated.
Awesome work!
Would you be open to accepting a PR (and activating a corresponding deployment) to generating the manifest schemas to JSON files and hosting them on GH Pages? This could enable the manifest.json features in other editors and IDEs as well. And from what I can tell, yours are the most up to date publicly available schemas.
I would really like to see PRs regarding to:
Right now schema is TS file and for now I would like to keep it this way. Once the project is more settled we can think about GH actions.
Project is open-sourced so if you want to do that… you can. You could also fork repo and add GH actions on your side and merge my project time to time.
What the other popular IDEs here except for VSCode?
I think that’s a good call. My idea would have been to use GH Actions to convert the TS to a JSON schema file and put it onto GitHub Pages. But totally fair if you would rather not integrate it (especially in the early stages). That’s why I wanted to ask before looking into how this could be implemented.
Fair. I don’t really have the capacity right now to maintain a fork-based project, so this won’t come from my end (maybe somebody else wants to do that, though?).
Personally, I heavily rely on JetBrains IDEs (for UXP mostly WebStorm). And while I love all the support annotations you implemented for VSCode, I wouldn’t want to maintain a plugin for the Jetbrains IDEs, trying to resolve conflicts between their native language support and the language server provided through Validator. Given that most of these IDEs support JSON schemas out of the box, all it takes for the manifest.json autocompletion support to be ported would be a hosted JSON schema that’s up-to-date.
JetBrains IDEs 
I personally use PhpStorm. But probably what @pklaschka wrote would be enough. IDK how this works, but if there’s a schema, I’d try to use it with someones help on how to set it up 
…so since I see 21 downloads and no issues reported I assume it works as it should? 
It worked great for me on my new plugins! Thank you!
FYI… I updated validation rules!
FYI… I did it again… new rules for UXP 8.0 ! 
Changelog: Release 1.2.0 · jardicc/vscode-uxp-validator · GitHub
Available here: Validator for UXP - Visual Studio Marketplace
I’ve released UXP Validator 1.3.3, my VS Code extension for Adobe UXP development.
This update is mostly about making validation more accurate as UXP and Adobe host applications keep evolving.
A few notable changes:
• Updated UXP version detection for newer Photoshop, InDesign and Premiere Pro releases
• Premiere Pro is now included in automatic host detection
• More accurate, version-aware validation for WebView permissions
• Support for new UXP 9.4 manifest feature flags
• Several CSS compatibility fixes and additions
• Fixed a race condition where older async validation could overwrite newer diagnostics while editing
That last one was particularly annoying — the validator could do the right work and still show you the wrong result.
If you already have it installed, VS Code handles the update automatically.
A few smaller things from 1.3.0–1.3.2, in case you missed them:
• Added Premiere Pro version support and improved host-version inlay hints
• Fixed manifest.json IntelliSense
• Fixed CSS diagnostics not updating correctly after document changes
• A few smaller compatibility fixes along the way
Release notes:
Issues, missing validation rules and feedback are always welcome.
