You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When binding a typeahead component instance to an existing v-model, the current value of the v-model property doesn't seem to be propagated to the input field; if a new value is typed in, or if the view model is changed from the outside, everything is propagated correctly. It's just the initial value which does not make it into the input field.
Then the code which does not work is the following; "does not work" in the sense that the pre-populated value of oidcClaim is not displayed in the input field.
Except when adding things to an array dynamically, where the typeahead element displays part of the dynamically added content (using this.value.someArray.push(...)... But I can live with that.
I'm having a similar issue with an edit screen. I need to wait for an ajax request to get the data and then apply it to the v-model used on the typeahead, but can't seem to get it to populate the textbox. The ajax function is even called in the component's mounted() method.
When binding a typeahead component instance to an existing v-model, the current value of the v-model property doesn't seem to be propagated to the input field; if a new value is typed in, or if the view model is changed from the outside, everything is propagated correctly. It's just the initial value which does not make it into the input field.
Version & browser
0.25.0, Safari and Chrome on macOS 0.13.5
Which component
Typeahead
Steps to reproduce the problem
Here,
standardClaims
is the following list:Then the code which does not work is the following; "does not work" in the sense that the pre-populated value of
oidcClaim
is not displayed in the input field.Expected behavior
The value of the property referenced in
v-model
is written into theinput
field initially.Actual behavior
The input field is always empty.
Thanks for your awesome work!
The text was updated successfully, but these errors were encountered: