Oh, I see
Or does serialize: false affect .get() as well as .serialize()?
@phillipskevin - the problem is that i can't data bind it - long story. there's something that's preventing the select from knwoing there's been a change in the option selected. i know (vaguely) that canJs has something that adds a value property to a select - but that doesn't seem to get updated. it knows there's a change, but the value on the select doesn't change, so i was hoping that maybe there's a way to access the change event that is generated with the ($change) function call
@phillipskevin i humbly disagree: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/select - it has selectedIndex but no value.
that's why I tried it in the JSBin... because it wasn't readily available on the docs you pointed out
it's in the DOM Interface link though
i can't bind to a property because of how the data is structured.
so, i just wanna be notified when there's a change, and check for the (hopefully) changed value, and act accordingly
<select class="form-control"
{($value)}="trainsByPlatform[platform.name]"
($change)="upsertInitialRelease(platform.name, scope.element.value)">
<option></option>
{{#each trains[platform.name] as train}}
<option value="{{train.name}}">{{train.name}}</option>
{{/each}}
</select>
is that the code you have?
so... I would first change
{($value)} to be only one-way bound
{$value}
so you only have one handler element->viewModel and one handler viewModel->element
right now you have a two-way binding and a one-way binding
yes, that was totally it. big sigh of relief
ok, since i got your attention (your awesome), those warnings are back. i have 100s of them
whoa, that's not it. sorry
can-stache-bindings: the event binding format ($click) is deprecated. Use on:click instead
(and removed in 4.0, which will be released very soon)
import CanLog from "can-log";
CanLog.logLevel = 99;
CanLog.logLevel = 99;