Closed frandiox closed 6 years ago
Good to know! I think that's something @johnleider should be able to fix for the next Vuetify alpha. 🙂
Don't threaten me with a good time! @KaelWD has there been any movement on this?
No, waiting for a response on that vue-meta issue.
I just pinged Sébastien on that issue, so hopefully it can be resolved soon. 🙂 Thanks to both of you for your work on Vuetify! I'll close this for now then, as there's nothing more that can be done from this repo.
@frandiox If you want to convince me to use metaInfo
instead of page
for the keyName
, I'm open to hearing an argument. 🙂 For me, I just felt that metaInfo
was a little too vague, it not being obvious that this is referencing page-level meta info in HTML. Would love to hear others' thoughts!
Thanks everybody!
@chrisvfritz The only argument would be that it's easier to look it up and see what's the library that provides it. Other than that, I'm perfectly fine with page
instead!
Hi! As of
vuetify@1.1.0-alpha.3
, it usesvue-meta
but hasmetaInfo
hardcoded in the source code. Therefore, changingkeyName
to something else breaks some theme-related functionality in Vuetify. This boilerplate usespage
instead ofmetaInfo
so it is incompatible for now.https://github.com/declandewet/vue-meta/issues/215
@chrisvfritz I guess there's nothing to fix here but I thought this information could be useful for somebody else :)