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

docs(migration): added migration instructions for ProsePre, ProseCode, and ProseCodeInline #2892

Merged
merged 1 commit into from
Dec 7, 2024

Conversation

JessicaSachs
Copy link
Contributor

πŸ”— Linked issue

#2885

❓ 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 handling of ProseCode, ProsePre, and ProseCodeInline have been updated in Nuxt Content v3. I didn't see instructions for this breaking change when I began my migration and opened a bug (it was not a bug, just a breaking change that hadn't been captured yet)

Resolves #2885

πŸ“ Checklist

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

@farnabaz farnabaz merged commit 1a364f5 into nuxt:v3 Dec 7, 2024
1 check passed
@franklin-tina
Copy link

Thanks @JessicaSachs

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.

MDC: ProseCodeInline being parsed as ProseCode
3 participants