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
When hovering over an entry we can now see only the title from the schema and that may prove not enough for some schemas that also have a longer description field too.
I mention that both title and description may be missing and we should use whatever we find.
One example from XML schemas can be used as a nice implementation example
Also the auto-complete field functionality does not display the field title after the name, something that is highly desired for ansible module arguments. Without this the user would be forced to first auto-complete the entry and make use of hover after in order to understand the purpose of that option.
The text was updated successfully, but these errors were encountered:
@evidolob Can you please give me some hints on how to test that PR? I always wondered how am I supposed to test yaml-language-server as the deliverable is not an extension, so I need to include it in a local build vscode-yaml but that was not clear to me.
When hovering over an entry we can now see only the
title
from the schema and that may prove not enough for some schemas that also have a longerdescription
field too.Ideally it should look like:
I mention that both
title
anddescription
may be missing and we should use whatever we find.One example from XML schemas can be used as a nice implementation example
Also the auto-complete field functionality does not display the field title after the name, something that is highly desired for ansible module arguments. Without this the user would be forced to first auto-complete the entry and make use of hover after in order to understand the purpose of that option.
The text was updated successfully, but these errors were encountered: