You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In all likelyhood, the LSP hints for our yaml fields are out of date in places. Go through the values and descriptions and cross check with documentation, updating where necessary.
The text was updated successfully, but these errors were encountered:
Spent a day getting confused by this trying to update the schema with latest from API. I think there's more work we can do here to make this process better. It feels like a waste of time to manually update the API schema to get along with the vscode extension schema, so I'm not going to do that now.
Path forward:
Let's settle on one method for adding descriptions to YAML fields. I say let's do this on API side so it will be done when folks are adding new fields. Then the extension side is really easy, just update the schema with the latest API version and convert to the correct format.
Achieving this will take some effort to
decide on a format for adding descriptions in API,
move the old descriptions over to API (removing from here),
adapt the conversion script to work with the format we settle on for descriptions, and
fill in any missing descriptions.
After all of this is done, we will be in a much better place for keeping everything up-to-date.
That said, there has also been talk of deprecating the YAML, so if that's going to be the case there's probably no point in doing any of this.
spalmurray-codecov
changed the title
[vscode] Audit LSP docs
[vscode] Revisit how we manage our YAML fields and descriptions
Nov 18, 2024
In all likelyhood, the LSP hints for our yaml fields are out of date in places. Go through the values and descriptions and cross check with documentation, updating where necessary.
The text was updated successfully, but these errors were encountered: