vueuse / head

Document head management for Vue. Powered by Unhead. - 🌇 Sunset

Home Page:https://unhead.unjs.io/setup/vue/installation

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Duplicate keyed tags being generated between pages (@vueuse/schema-org)

AleksejDix opened this issue · comments

commented

looks like https://vue-schema-org.netlify.app/ relies on the old version of the plugin.

Your help might be needed to make Schema work with new Version

Hey @AleksejDix

This may be fixed, can you try upgrading @vueuse/schema-org to v1.1.0-beta.6

commented

@harlan-zw after upgrade to https://github.com/vueuse/schema-org/releases/tag/v1.1.0-beta.6

ld+json blocks display content, but there are multiple blocks at the same time

You can reproduce it when navigation in a spa mode. On every navigation new script is added.

Bildschirmfoto 2022-11-13 um 18 38 42

Bildschirmfoto 2022-11-13 um 16 49 20

Thanks for flagging this @AleksejDix

The duplicate tag being created is fixed in the latest version (1.0.7) as far as I can tell, let me know if you still have any issues :)

commented

Waiting for 1.07 to be released :D then i can confirm the fix

Great work!

Thx for making those changes so quickly.

Thanks :)

Should be out and ready to go, in fact, I'm up to 1.0.10 now 😆

commented

There are still Issues

Issue 1
Demo: https://schema-json-lg.pr.propertycaptain.ch/en/faq

FAQ
<SchemaOrgQuestion v-for="faq in meataQuestions" :key="faq.id + language" :name="faq.question" :accepted-answer="faq.answer" > </SchemaOrgQuestion>

Question are not getting removed after navigation to AboutUs page
Also Question Do not change when Language of the site is changes - Language is changes based on route aliases.

Issue 2

if Title is empty no fallback from TitleTemplate function is shown.
<title> tag is missing completely on this pages

I believe the reactivity issues are issues with @vueuse/schema-org itself, I'll look into it soon once @vueuse/head is stable. Reactivity isn't a major issue anyway though, it's only meant to be implemented in dev because in production only the initial schema-org will be used.

For issue 2 would you mind providing an example? Is this specific to the schema-org or @vueuse/head

Feel free to contact me on discord if you want to debug it togethor