-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Add support for "multiple" select #41
Comments
I'll let @n1k0 ponder, he's our local json-schema expert (if you ask him, he'll say he's not, but that's lies) |
@almet Haha, hmpf, thanks I guess. Yes, we need to deal with a specific kind of array widget when the schema is constrained with an enum of strings (possibly numbers, integers, datetimes too) so we can render a select field (or a list of checkbox btw) instead of the regular The only thing is that with such a schema, one might want to allow multiple occurrences of an allowed Also, re |
Actually while googling for solutions I've just stumbled upon the Choices v5 proposal, which is probably something we'll want to support if it makes it to the spec eventually. |
And so for ensuring a multiple choices field can't be mistaken for a multiple occurrences of choices field, there's is that UniqueItems proposal. Edit: |
Okay, so to sum up I can start working on supporting schemas like this :
resulting on a multiple select (and maybe alternatively a list of checkboxes). Is that it ? |
That's a good summary of it, yes. Thanks you so much on planning to help and contribute! |
I just finished the work on this issue. However, I can not push my branch upstream to make my pull request. Could you give me the rigths on the repo or do you prefer that I make my pull request from a fork ? |
Yes please do it from a fork, you could also give us some contributors roles on your fork if you want us to collaborate on your branch. |
Fixed by #42. |
I need to be able to create select fields with the possibilty to select multiple values.
I can work on it but I'm not sure which way I should go with jsonschema.
My intuition is to use a schema that looks like this :
maybe with an alternative widget
multiselect
for example.What are your opinions about this ?
I will probably also need to support enumNames (See https://github.com/json-schema/json-schema/wiki/enumNames-(v5-proposal) )
The text was updated successfully, but these errors were encountered: