Idea: Extension for VS Code

[gjsjohnmurray]

I just created https://ideas.intersystems.com/ideas/DPI-I-602 to gauge interest in a possible VS Code extension for a more visual UX. Upvotes there are welcome, as are comments.

[isc-tleavitt]

@gjsjohnmurray thanks - this is a great idea.

A large part of the motivation/need for such a tool is the set of significant usability issues with module.xml as it currently stands. I'd like to do the following things to improve it:

• Make it easier to enumerate resource processor classes and their attributes, leveraging existing /// documentation ((Re?)introduce SASchema for .ZPM document type and update for "unwrapped" format #502 would ideally incorporate this) - the benefit of (Re?)introduce SASchema for .ZPM document type and update for "unwrapped" format #502 is mostly contingent on XML completion for %Studio.AbstractDocument subclasses language-server#334 but if there was a GUI it would benefit from cleaner, documented APIs around resource processors and similar constructs
• Improve the usability and capabilities of zpm "generate" to provide a CLI alternative for those who prefer that mode

Historically, the HealthShare Package Manager had a %Studio.Extension UI with menus for various package manager-related things, along with a way to compose %Studio.Extension.Base subclasses to allow it to be used alongside source control. This got taken out from the initial ZPM fork and isn't in 0.9.0 either but I'd love to see it reintroduced, even if as a separate/optional component. #501 is a prerequisite to doing things better server-side.

[gjsjohnmurray]

I have created https://openexchange.intersystems.com/package/IPM-in-VS-Code and entered it into the current contest. I'm continuing to add features, and contest voting is open!

[isc-tleavitt]

I have created https://openexchange.intersystems.com/package/IPM-in-VS-Code and entered it into the current contest. I'm continuing to add features, and contest voting is open!

Amazing - great to see, thank you @gjsjohnmurray !