-
Notifications
You must be signed in to change notification settings - Fork 20
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
Document Associative Arrays #21
Comments
This specification has not been supported yet, I'll update later if you need. @barnaclebarnes |
@zhandao That would be great. We are using this in quite a few places where were have translated fields. Now that I am starting to get my head around how this all works I'm loving it. Thanks! |
Hi, please update this gem from GitHub, and try it like f330d41#diff-917ffdde79050994c60fead0486d60fcR211 Here are two ways to define this specification:
|
I think I have the additionalProperties outputting as per the proper spec but I think there is a bug in that every item now has
|
data: {
name: { type: '{=>string}' },
additionalProperties: { type: 'string'}
} Means that TWO fields in your form data body -- "name" and "additionalProperties". "additionalProperties": {
"type": ""
} is a bug, I had fixed it, please update this gem. |
data: {
name: { type: '{=>string}' },
}
# or
data: {
name: { type: Object, additional_properties: 'string' }
} are right ways. |
All seems to work now. |
To output this:
We should be using a Dictionaries, HashMaps and Associative Arrays
This uses the
additionalProperties
but deifning this doesn't seem to work:name: {type: Object, additionalProperties: String}
Outputs
But should output (I think):
The text was updated successfully, but these errors were encountered: