Add explicit (Opt-In?) support for hidden fields by item

[knalli]

Currently, exactly one hidden field will be synchronized every time a selection has changed. Doing this, the hidden input field holds a comma separated list of id values.

We're planning to change or modify the behavior (with options) that for every selection a hidden input field will be generated.

Instead of

<input type="hidden" name="as-hiddenfield" value="1,2,3" />

that would be

<li>
  <input type="hidden" name="as-hiddenfield[0]" value="1" />
  ...
<li>
<li>
  <input type="hidden" name="as-hiddenfield[1]" value="2" />
  ...
<li>
<li>
  <input type="hidden" name="as-hiddenfield[2]" value="3" />
  ...
<li>

Would this be helpful?

[ivirabyan]

Don't know why someone might need this, you can always split on server side. And it is not consistent - I give a joined string to the widget, but get back an array. Anyway, glad you decided to maintain the project. I think it would be usefull to optionally allow creating new item by space key (not only comma or tab), of course optionally.

[knalli]

Well, think about valid models transporting between the frontend (JavaScript) and the backend (let's say Java or PHP).

Thank you for the idea of space, I'll make a new issue for this. Nice idea.