Use a custom keyName dynamically

[KaelWD]

In vuetify we use vue-meta if this.$meta exists, but I had to hard-code metaInfo and head (for nuxt). Is there a way for my library to dynamically use whatever keyName the end user passed in?

• https://github.com/vuetifyjs/vuetify/blob/d724779defded93f887afb257869063fc22d0b43/src/components/VApp/mixins/app-theme.js#L61-L83
• fix(ssr): allow theme to be applied with vue-meta vuetifyjs/vuetify#3314
• refactor(theme): use metaInfo() and nuxt() instead of hacking $options vuetifyjs/vuetify#3488

[atinux]

Hi @KaelWD

What if you could get it trought this.$meta().options.keyName?

I believe we should add it here: https://github.com/declandewet/vue-meta/blob/master/src/shared/%24meta.js#L14

Please mention me so I can get an email to follow this issue.

[KaelWD]

Yeah that should be good. Do you know how I could use that though? I had this before which worked fine in SSR, but I think caused a race condition on the client-side because it would sometimes not apply.

[chrisvfritz]

@atinux Just mentioning you on this as you requested. 🙂

[miniplus]

Just ran into this issue with vuetify having the hardcoded value and my project using a different keyName. Took me quite some time to debug.

As this issue is half a year old, has this been considered? Just looking for an update @atinux.

Thanks! 🙂

[pimlie]

vue-meta v2 will add a getOptions method so you can call this.$meta().getOptions().keyName

[theprojectsomething]

@pimlie this.$meta().getOptions() is currently listed in the 1.6 API docs: https://vue-meta.nuxtjs.org/api/#meta-getoptions

[pimlie]

This issue has been closed as changes for it are included in the v2 release candidate. Please help us testing the release candidate and report any follow-ups in a new issue