@adrienbaron I've recently noticed that I'm getting the following warning:
vue.esm.js:629 [Vue warn]: Invalid prop: type check failed for prop "step". Expected Number with value 2, got String with value "2"
for router query properties that are non-string. The current implementation of vuegwt router forces us to pass in Strings. Is that something you could fix? Or am I doing something wrong?
@mdavis95 @payammeyer this also means that boolean props in Vue GWT now behave like in Vue.
Let’s say you have this prop declared:
@Prop boolean myProp
Not passing it to your component will now make it false by default instead of undefined.
Also, passing it just as an attribute that you don’t bind will set the prop to true:
<my-component my-prop />
Vue does that for a prop when you tell it it’s type is a JS Boolean, which we now do by default as mentioned above :+1:
We have an MR being prepared by @jtrentes that also improves support for Java Boolean Prop. Not binding those will results in
null by default, and passing it as an attribute will result in true (to get false you bind explicitly false)