Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

serverPrefetch in a v-for loop gets overwritten #46

Open
ovlb opened this issue May 18, 2022 · 1 comment
Open

serverPrefetch in a v-for loop gets overwritten #46

ovlb opened this issue May 18, 2022 · 1 comment

Comments

@ovlb
Copy link

ovlb commented May 18, 2022

I’ve come across a kind of weird caching (I guess) issue.

I’ve a page which uses a headless CMS with content blocks. One of those blocks renders markdown:

<template>
  <div v-for="block in content" :key="block.id">
    <content-markdown
      v-if="block.__component === 'content.text'"
      :md="block.text"
    />
  </div>
</template>

I wanted to utilise this.renderTemplate in serverPrefetch.

  async serverPrefetch() {
    this.renderedMd = await this.renderTemplate(this.md, 'md')
  },
<template>
  <div class="md-content" v-html="renderedMd" />
</template>

This, though, leads to a problem, as suddenly all paragraphs on the page show the same content.

Screenshot of a website where every rendered template block shows the same content

The shown content is the one of the last block. So somehow it overwrites everything that has been rendered before.

If I use a synchronous function directly in the template this issue does not occur.

I use @11ty/[email protected] with @11ty/[email protected]

Any idea what happens here?

@ovlb
Copy link
Author

ovlb commented May 18, 2022

I poked a bit more at this and the problem only occurs if the result of renderTemplate is saved to the component data.

export default {
	data() {
		return { renderedMd: '' } 
	},

	async serverPrefetch() {
    	this.renderedMd = await this.renderTemplate(this.md, 'md')
  	},
}

if renderedMd is not present in data it works as expected.

Now I don’t know if this is a bug or a caveat?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant