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

Unexpected non-props attributes falling-through when using ContentRenderer #2208

Closed
TechAkayy opened this issue Aug 1, 2023 · 4 comments
Closed

Comments

@TechAkayy
Copy link

TechAkayy commented Aug 1, 2023

Environment

Nuxi 3.6.5 1:03:30 PM
1:03:30 PM
RootDir: /Users/techakayy/Templates/happy-paws-with-nuxt-tailwindcss 1:03:30 PM
Nuxt project info: (copied to clipboard) 1:03:30 PM


  • Operating System: Darwin
  • Node Version: v18.12.1
  • Nuxt Version: 3.6.5
  • Nitro Version: 2.5.2
  • Package Manager: npm@8.19.2
  • Builder: vite
  • User Config: runtimeConfig, modules, pinegrow, css, postcss, content, unocss
  • Runtime Modules: @pinegrow/nuxt-module@3.0.3, @unocss/nuxt@0.54.1, @nuxt/devtools@0.7.1, @nuxt/content@2.7.2, @vueuse/nuxt@10.3.0
  • Build Modules: -

Reproduction

https://github.com/pinegrow/happy-paws-with-nuxt-tailwindcss

The warnings are thrown only during development. In prod build, the document seems to render fine, https://happy-paws-with-nuxt-tailwindcss.netlify.app/, though the warning makes us wonder if we have got something wrong. Please advise me of any incorrect usage in the below explained context.

Describe the bug

  1. Clone the above repo, install dependencies, and start dev-server npm run dev
  2. Open app in browser, and have browser devtools console open
  3. Navigate to a blog post (under hamburger menu), for eg. http://localhost:3000/blog/vue-3-3
  4. The following unexpected warnings are thrown
image

Additional context

In pages/blog/[...slug].vue, I'm using the ContentRenderer component to render a document coming from a query. I'm not passing any classes to this component, just the post (second screenshot).

image

image

Logs

Thanks for looking into this.
@nobkd
Copy link
Contributor

nobkd commented Aug 2, 2023

This was caused by <ProseCode> (see #2111) and should theoretically be fixed in edge channel (see #2187 with this general change #2121 (comment))

@TechAkayy
Copy link
Author

Thxs bunch for the update 😀

@farnabaz
Copy link
Member

farnabaz commented Sep 1, 2023

Fixed in 2.8.

@farnabaz farnabaz closed this as completed Sep 1, 2023
@TechAkayy
Copy link
Author

Thank u 🙏🏾

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

3 participants