-
-
Notifications
You must be signed in to change notification settings - Fork 266
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
Name suggestion for patternProperties #634
Comments
@fkorotkov could you provide some examples of what you mean? |
Sure! For example in my case, I was working on a schema for Cirrus CI: SchemaStore/schemastore#488 There I have such pattern property: "patternProperties": {
"(.*)task": {
...
}
} Which means there can be multiple tasks defined. Tasks like I would love to add such suggestions within a schema so editors can use them and do suggestions. "patternPropertyExamples": ["build_task", "test_task", "lint_task", "deploy_task"],
"patternProperties": {
"(.*)task": {
...
}
} I created this issue just for a record of my use case. Maybe some other people will find it useful too. It's not something very important, but can definitely be useful for schemas that use |
This sounds like a good candidate for a schema extension keyword, a concept that @handrews, myself, and a few others have been discussing over several issues. In short, you would be able to define your own keywords, what they mean, and how they interact with the rest of the schema. Personally, this feels like an application-level feature (live value suggestion as the user types) rather than something that would produce an output during validation or annotation collection. |
Is there an issue to support |
The primary one would probably be #602 right now. It links to a bunch of other issues that relate to it. |
Thank you, all! Closing this issue. Will watch #602 |
It will be nice to have a way to list some possible options for a pattern property so an IDE can suggest these options for completion.
The text was updated successfully, but these errors were encountered: