Mike Amundsen
Mike Amundsen
adding support for `checkbox`, `radio`, and `select-options` via `suggest` constuct from #6 note that this might also be a way to deal with `enums` (see #38)
@jenzopr good catch. feel free to do a PR on that and I'll merge it in ASAP.
Currently, `value` is defined as a string, not an array. changing this can break existing implementations. if you want to return something other than a string, you need to use...
[snip] "text" would need further description, [/snip] Not sure what this means "further description" you mean that it adds a new property to CJ? or something else?
@mrdevinmob yes, the `text` property would need to be documented for this extension. similar to the way `options` and `multiple` are in this extension already.
thanks for the follow up and posting the gist. it looks pretty clear. style-wise, the content is just fine. anyone else want to weigh in here? is it OK w/...
yes, if we can come up w/ a stable extension for the data element that mimics the "select" control for HTML, it could be applied to the data element in...
where are we on this? On Mon, Oct 1, 2012 at 4:46 PM, Cameron Bytheway [email protected]: > I wanted to get a discussion going about setting the content type of...
@nnworkspace thanks for the feedback. love to see your thoughts on this. 1) ALPS is not a definition format like OAS, RAML, AsyncAPI, proto3, gQL, or other interface definition languages...
see https://github.com/alps-io/mapping/issues/2 on the ALPS side.