Mike Amundsen
Mike Amundsen
@robertovelasco all cool with the above. also, what i meant w/ saying that `suggest` is an _optional_ element is that a HAL-FORMS processor (library, framework, etc.) would not be REQUIRED...
@nickshanks Note that the current implementation includes support for a google-style "type-ahead" UX. From the human UI POV, the name/value pairs could be rendered as an HTML INPUT with type-ahead...
not sure i see anything changed to the HAL-FORMS spec. am i missing something?
`suggest` _ah, yes!_ sorry, we've spent so much time on other things! yes, i'll add the suggest material as an OPTIONAL property. i'll complete it this week.
Yes, add an issue. Good idea. On May 26, 2016 01:45, "Joseba Ander Ruiz Ayesta" [email protected] wrote: > @mamund https://github.com/mamund We are testing different situations > with Suggest and I...
Yes, this is top priority this week. Let me read through and ping you back here shortly.
@odrotbohm : OK, i think we're super close here. i appreciate the work (and the patience) of you, @anderruiz , @robertovelasco , and others on this. Can you help me...
@evert : good to hear. we can talk about `x-ww-forms` as long as we stay focused on the `suggest` element. would really like to get this one knocked out.
yep, i meant to address this with this bullet > we'll need to explain how selected value(s) are represented in the property.value attribute. esp. if we support multi-select i think...
seems reasonable. can you work up a HAL-FORMS example for review?