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

fix(renderer): do not ignore component objects #3127

Merged
merged 1 commit into from
Feb 18, 2025
Merged

Conversation

farnabaz
Copy link
Member

πŸ”— Linked issue

reported in #2148 (comment)

❓ Type of change

  • πŸ“– Documentation (updates to the documentation or readme)
  • 🐞 Bug fix (a non-breaking change that fixes an issue)
  • πŸ‘Œ Enhancement (improving an existing functionality like performance)
  • ✨ New feature (a non-breaking change that adds functionality)
  • ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

πŸ“š Description

The content Renderer was ignoring components in the resolve function. The component object should be passed down to the MDC renderer.

πŸ“ Checklist

  • I have linked an issue or discussion.
  • I have updated the documentation accordingly.

Copy link

Deploying content with Β Cloudflare Pages Β Cloudflare Pages

Latest commit: b7e21c1
Status:Β βœ…Β  Deploy successful!
Preview URL: https://6b5b26d6.content-f0q.pages.dev
Branch Preview URL: https://fix-custom-components.content-f0q.pages.dev

View logs

Copy link

pkg-pr-new bot commented Feb 13, 2025

npm i https://pkg.pr.new/@nuxt/content@3127

commit: b7e21c1

@farnabaz farnabaz merged commit 8a66225 into main Feb 18, 2025
4 checks passed
@farnabaz farnabaz deleted the fix/custom-components branch February 18, 2025 12:36
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

Successfully merging this pull request may close these issues.

1 participant