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

Angular getLocalization() does not have access to value defaultResourceName. #22245

Open
1 task done
rsoulard opened this issue Feb 28, 2025 · 0 comments
Open
1 task done
Labels

Comments

@rsoulard
Copy link

rsoulard commented Feb 28, 2025

Is there an existing issue for this?

  • I have searched the existing issues

Description

While searching this issue, I did find two similar examples, but they were not helpful.

I noticed that the title of my pages can not be localized. Digging deeper, I discovered that getLocalization() in the Angular LocalizationService receives NULL when accessing state.localization.defaultResourceName. It feels like this value should be set to the value configured in environment.ts under localization but even with that configured the value of state.localization.defaultResourceName is still null.

Reproduction Steps

  1. Create a microservice template solution with Angular and Localization.
  2. Note that, once running, the page title for angular is always "MyProjectName".
  3. Verify that environment.localization.defaultResourceName has a value in environment.ts.
  4. Attempt to set "AppName" in the Angular localization.
  5. See that this has no effect as getLocalization() can not resolve a defaultSourceName and will not point to ::AppName

Expected behavior

Setting environment.localization.defaultResourceName in environment.ts should set a value for getLocalization() to use.

Actual behavior

getLocalization() receives NULL when attempting to access state.localization.defaultResourceName

Regression?

I do not know.

Known Workarounds

No response

Version

9.0.4

User Interface

Angular

Database Provider

EF Core (Default)

Tiered or separate authentication server

Separate Auth Server

Operation System

Windows (Default)

Other information

No response

@rsoulard rsoulard added the bug label Feb 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant