Skip to content

feat(ui): Add support for localization nodes #8539

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.

Sign up for GitHub

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

Merged
jacekradko merged 6 commits into from
May 15, 2026
Merged

feat(ui): Add support for localization nodes #8539

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
f458610
feat(ui): Add support for localization nodes
alexcarpenter May 13, 2026
3ad12d4
Update applyMarkupToNodes.test.tsx
alexcarpenter May 13, 2026
b5821f7
simplify
alexcarpenter May 13, 2026
bd37b52
performance optimization
alexcarpenter May 13, 2026
d19f13e
add defense test cases
alexcarpenter May 13, 2026
4fe4353
Create inline-bold-localization-markup.md
alexcarpenter May 13, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions .changeset/inline-bold-localization-markup.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
---
'@clerk/ui': minor
---

Add support for inline `<bold>` markup in localization values, rendered as `<strong>` elements. Translators can now write `'Agree to <bold>Terms</bold>'` in a single key instead of splitting into prefix/bold/suffix fragments. Token values are substituted only into parsed text leaves, so user-controlled data can never become markup. Also hardens `applyTokensToString` to use `Object.prototype.hasOwnProperty.call` when filtering token names, preventing prototype-chain names like `{{hasOwnProperty}}` from crashing rendering.
Loading
Loading