-
Notifications
You must be signed in to change notification settings - Fork 237
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Help user set the schema of current YAML file #62
Comments
@JPinkney when is the next release window for vscode-yaml in market-place? |
@andxu Should be this monday! |
Can we close this? |
Is there a place where the schema being used is displayed on the editor? |
I have to confess that I have the same problem. This extension should expose the Schema used somewhere, probably in the status line. The tooltip on YAML could be an useful place. I have no clue which schema was used in a file, if any at all. For someone trying to write schemas this is double annoying. |
I would be OK with having a way to show which schemas are associated with the currently open file but I'm just now sure how. The status bar is already generally crowded and how should we display them on the status bar when there is multiple schemas associated with a yaml file? |
Tooltip or the icon should be ok. It would avoid avoid cluttering the statusbar. |
…vanced Changed autocompletor to support code completions redhat-developer#2…
Closing as not solvable by us. If vscode adds a different way to assign schemas to JSON files, we can look into matching the same feature. |
Currently, a user needs to specify schemas by modifying the settings.json.
Here to propose a status bar item to show the current schema for the current YAML file. Users can tell what schema is currently used and can switch schema by clicking on it.
This is useful when the wildcard is supported when associating schemas with YAML files.
The list of available schemas is maintained by the YAML extension. It will also allow other extensions register new schemas. It can also work with the mechanism proposed in #61 to automatically associate schemas with YAML files.
The text was updated successfully, but these errors were encountered: