@lionel-bijaoui could you check this problem?
Reproduction:
npm run devNew button
I going to check this today.
Thank you!
Ok so vue-multiselect don't like to have an undefined value and crash.
So is it a multiselect bug? Are we report it?
I'm raising an issue right now
Great! Thanks!
We have green light for this
Could you test it in dev?
Yes
@icebob I still have a problem. :disappointed:
I have changed some information, clicked save, clicked another profile then clicked back to the original profile and the data where still here. I got no error message in the console.
But when I do new, same error message.
I can't find where the error is happening...
Edit: maybe rawgit is not yet updated ?
I dont think so rawgit cached.
We need to create a fiddle with this issue to monterail, no?
Well, they have fixed monterail/vue-multiselect#88 but not monterail/vue-multiselect#80
ohh, my mistake. Sorry.
No pb, I did the same mistake
This problem is alive. I tested. I created a fiddle for developer of multiselect.
They don't like to have an undefined or null value. Maybe we could prevent it ?
But on the website in the "Basic Usage", he uses value: null
Fixed in 2.0.0-beta15