Closed a-Leong closed 4 years ago
Thanks for creating the issue, this should be fixed soon with a newer version of ionic/core, the issue as you've noticed is the casing, unfortunately with Vue3 it's impossible (at least for the time being) to force prop and event casing, I've worked with the ionic team on this and the result is the ability to define custom casing when registering custom elements. I plan on getting this resolved within a few days as tops.
I've just looked at it again and it doesn't have to do with anything I've described above, will try to reproduce it locally, have you tried using IonMenu instead of ion-menu?
Yes, same issue using IonMenu
I've just tried with the same versions as you, everything seems to be working just fine, here's the ionic/vue3 examples app I'm testing everything with: https://github.com/michaeltintiuc/ionic-vue-3-example
Try removing node_modules and reinstalling, for some reason it seems like updating to newer versions without doing that breaks stuff
I had tried removing and reinstalling node_modules, but after your suggestion I removed package-lock.json as well and that did the trick. Thanks so much for your help!
Edit: This also resolved several other inexplicable issues and warnings 🤩
Happy to help!
In Vue 3 prerelease
I'm encountering a consistent issue where the IonMenu's required
contentId
attribute is not recognized. The menu does not work, an error is thrown and these messages appear in the console:Inspecting the IonMenu element, the attribute is
contentid
(incorrectly cased). Occasionally, hot-reloading after a modification to the file containing the IonMenu temporarily fixes the issue and in those cases the attribute is correctlycontent-id
.Replicated in sample app: