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
I'm trying to use v-select in a Laravel/Vuejs project.
When submitting my form with a POST method, the input is not recognized as such since v-select doesn't give it the name attribute I passed it.
Nonetheless, I feel my component is alright since it's data is updated on input change.
A generated html5 input with the name attribute passed to v-select as :inputName
A generated html5 input with a value attribute reflecting the value of v-model's target
Actual behavior
A generated div (with the name attribute) which contains an input type search (without name)
No value attribute in any of the generated html code
Desktop (please complete the following information):
OS: Ubuntu 18.04.3
Browser: Firefox 70.0
I'm not sure this is an issue but I've spent my day looking for solutions without finding any working clue.
Seems to me I'm following the documentation alright...
Please tell me if I missed something in the doc or if this is really an issue.
Best Regards
The text was updated successfully, but these errors were encountered:
Hi,
I'm trying to use v-select in a Laravel/Vuejs project.
When submitting my form with a POST method, the input is not recognized as such since v-select doesn't give it the name attribute I passed it.
Nonetheless, I feel my component is alright since it's data is updated on input change.
Here is my component :
In the parent, I give my component some values for its props :
<selector name="techno[]" id="techno" :tags={{ $tags }}></selector>
And here is the generated html :
Expected behavior
:inputName
Actual behavior
Desktop (please complete the following information):
I'm not sure this is an issue but I've spent my day looking for solutions without finding any working clue.
Seems to me I'm following the documentation alright...
Please tell me if I missed something in the doc or if this is really an issue.
Best Regards
The text was updated successfully, but these errors were encountered: