Skip to content

fix(i18n): support both string and object forms of i18n.sourceLocale #859

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

eintim
Copy link

@eintim eintim commented Jun 4, 2025

The original implementation assumed sourceLocale was always a string. However, Angular allows it to be either(see schema):

  • A simple string (e.g., "en-US")
  • An object with properties like code, subPath, and baseHref

When an object was used, the resulting output path included [object Object], causing incorrect output paths or build failures.

This fix ensures compatibility with the full range of valid sourceLocale definitions

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