Vue props validation error

[LexSwed]

Vue version 2.5.11 complains on "twoWay" prop for a list of objects
vue2-google-maps version is 0.8.4

[asifm]

Seeing this in several other plugins. Pretty sure it's related to these changes, as mentioned in https://github.com/vuejs/vue/releases

Improvements

warn misspelled keys on prop validation object (#7198) d02bb37, closes vuejs/vue#7198

[jdriesen]

Hi All,

Encountering the same problem...
Can smb please tell me how to solve this ?

Thanks in advance,
Johnny

[Arwany]

I am also getting a lot of these warnings:

[Vue warn]: Invalid key "twoWay" in validation rules object for prop "center".

[asifm]

Seems it's just warnings. You can safely ignore them until it's fixed here. Or you can go back to the previous version of vuejs (2.5.10).

[LexSwed]

@asifm despite it's just warnings, it breaks Vue and app doesn't work.

[asifm]

I just went back to vue 2.5.10. Things are fine now. Make sure you downversion the other packages that have to match vue version. In my case they were vue-template-compiler and vue-server-renderer.

[jdriesen]

Thanks for this valuase info, @asifm.
If I can ask, which version of vue-template-compiler and vue-server-renderer are you currently using ?
(with vue 2.5.10 ?)

Thanks in advance for your reply.

Johnny

[asifm]

They have to always match the vue version. So they'll also be 2.5.10

[jdriesen]

Problem solved (running now on 2.5.10)
Thank you, @asifm

[vesper8]

so.. are we waiting for vue to fix this or are we waiting for vue-google-maps to fix this? I know it's just a warning.. but I don't like locking my vue version

[asifm]

@vesper8 We're waiting for all the libraries to fix and update. Vue has nothing further to do about it. 2.5.11 hasn't brought much change (other than this one), so going back to 2.5.10 seems a good solution for the time being.

[Arwany]

I have read somewhere that since Vue has added some spellchecking for props keys, it will always warn.

Here is the commit link

[jdriesen]

Yep, indeed @Arwany ...

It WAS a problem in 2.5.11...
Though it's solved now in Vue v. 2.5.12 (released since a couple of hrs...)

Grtz,
Johnny

[asifm]

Please close the issue. Vue 2.5.12 (and later versions) won't cause this problem.