Skip to content

fix: Correctly compile messages containing escaped curly braces (e.g. '{name'}) - #1950

Merged
amannn merged 1 commit into
mainfrom
fix/1948-escaping
Jul 2, 2025
Merged

fix: Correctly compile messages containing escaped curly braces (e.g. '{name'})#1950
amannn merged 1 commit into
mainfrom
fix/1948-escaping

Conversation

@amannn

@amannn amannn commented Jul 2, 2025

Copy link
Copy Markdown
Owner

Fixes #1948

@vercel

vercel Bot commented Jul 2, 2025

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
next-intl-docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jul 2, 2025 7:53am
next-intl-example-app-router ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jul 2, 2025 7:53am
next-intl-example-app-router-without-i18n-routing ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jul 2, 2025 7:53am

@amannn amannn changed the title fix: Compile messages containing escaped curly braces (e.g. '{name'}) fix: Correctly compile messages containing escaped curly braces (e.g. '{name'}) Jul 2, 2025
@amannn
amannn merged commit 4d418f4 into main Jul 2, 2025
7 checks passed
@amannn
amannn deleted the fix/1948-escaping branch December 29, 2025 14:34
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.

Escaping differs between dev and build

1 participant