Skip to content

fix: preserve locale casing in content collection entry IDs#1447

Open
lirenjie95 wants to merge 1 commit into
processing:mainfrom
lirenjie95:fix/content-entry-id-locale-casing
Open

fix: preserve locale casing in content collection entry IDs#1447
lirenjie95 wants to merge 1 commit into
processing:mainfrom
lirenjie95:fix/content-entry-id-locale-casing

Conversation

@lirenjie95

@lirenjie95 lirenjie95 commented Jun 16, 2026

Copy link
Copy Markdown
Contributor

Closes #1446

The original issue was introduced in #1409

@lirenjie95 lirenjie95 force-pushed the fix/content-entry-id-locale-casing branch from c54c07b to 13af1c0 Compare June 17, 2026 01:50
@Nwakaego-Ego

Copy link
Copy Markdown
Collaborator

Hi @lirenjie95, thank you for the PR. Tested this locally and can confirm the fix works, Chinese translations now load correctly after switching language. Placing generateEntryId in shared.ts is the right call, that file already holds shared utilities used across collections. One place to maintain, all 12 collections benefit.
cc @ksen0 @doradocodes

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.

[Tutorials] Tutorial content remains in English after switching language

2 participants