Multi-select binding behaviour incorrect about bind-middleware

[solkimicreb]

Thats right multi select is not yet implemented. Data binding uses HTMLSelectElement.value for the binding - which is the first selected value in case of a multi select (according to the spec).

I guess shelly should be an array of the selected values, in your case. It needs to be reworked a bit to support this. I would ask if you are interested in submitting a PR, but currently setting up the project locally is pretty painful because of the modular nature (lots of repos) 😄. I plan to make things more community and PR friendly for the next release and i will squeeze in a fix for this too.

Thx for the issue, I will keep it open until the fix arrives!

[solkimicreb]

This works as a one way binding in the meantime, if that's enough for your use case:

const map = Array.prototype.map  
nx.components.app()
	.use((comp, state) => {
		state.names = ['John', 'Ann', 'Joe']
		state.onchange = (ev) => {
			state.selected = map.call(ev.target.selectedOptions, option => option.value).join(', ')
		}
	}).register('my-app')

<my-app>
  <select name="selected" multiple #change="onchange($event)">
    <option value='John'>John</option>
    <option value='Ann'>Ann</option>
    <option value='Joe'>Joe</option>
  </select>
	<p>@{selected}</p>
</my-app>

[solkimicreb]

@jaypha I fixed it: nx-js/bindable-middleware@f3bb59f.

Now your example would set selly to an array of values. Just run an npm i to get the latest version (1.0.2) of the bindable middleware. I will wait to see if it works for you before closing this (:

[jaypha]

I just tested the new fix, and this appears to work fine. Thanks.

[solkimicreb]

Great! I am closing this issue then.