Improve native format (.ga) schema

[davelopez]

With #18, #19, and #20, we can now get a great deal of functionality out of the native .ga format schema definition but the schema is largely incomplete and inaccurate (initial version generated by an existing sample workflow).

How to improve it

The schema is easy to extend and improve, in addition to the standard JSON schema properties defined in the documentation, we can use some custom properties supported in VSCode to use Markdown formatting in hovers or insert snippets.

Parts that need improving

• Document existing properties using the markdownDescription attribute.
• Add missing properties
• Add correct properties to required and leave out the optional ones
• Fix incorrect type assignments to properties
• Add default values or possible enum values to properties with known values
• Add defaultSnippets where auto-completion can be beneficial

[jmchilton]

Can you add me to the project and assign me to this! Also you've had a couple more years of galaxy-language-server development since this project was last touched - is this still the right approach broadly for this kind of thing? I'm going to use to showcase and make user-friendly all of the work in galaxyproject/galaxy#21971 - so I want to make sure this is still on the right track and there aren't... I don't know obvious other approaches to IDE integration that have popped up - I have no knowledge of these plugins, systems, etc.. and I would love you perspective from a high-level.

[davelopez]

Awesome! Thank you so much for pushing this forward! Now is the perfect time to revive this project with all your recent improvements around Format2 🙏

I haven't touched this in a very long time, but I think the LSP approach is still relevant. There are, for sure, new improvements in the protocol that we can integrate and dependencies to update, etc. But I'm not aware of a better approach for this.

Regarding the .ga format schema support that motivated this particular issue: the idea was to make it somehow "useable" for manually or programmatically fixing some issues that users like Wolfgang were experiencing reviewing or maintaining workflows in IWC. But it was a temporary thing while waiting for the proper Format2 first-class support in Galaxy and IWC, so we don't really need to support .ga If we want to focus now on Format2, which is ready or almost there.