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

Translation for thread #3094 #3120

Merged
merged 1 commit into from
Aug 8, 2023
Merged

Translation for thread #3094 #3120

merged 1 commit into from
Aug 8, 2023

Conversation

leigh-pointer
Copy link
Contributor

Updated the Missing or incorrect keys

Updated the Missing or incorrect keys
@sbwalker sbwalker merged commit 0d0909a into oqtane:dev Aug 8, 2023
@sbwalker
Copy link
Member

sbwalker commented Aug 8, 2023

@leigh-pointer thank you! One item I noticed is that the Section component should not need to use the Localizer to assign properties:

Heading=@Localizer["Settings.Heading"]>

You should be able to have a property of ResourceKey and Heading with values in English and at runtime the framework will look in the RESX file for a key of "ResourceKey:Heading" to get the translated value

@leigh-pointer
Copy link
Contributor Author

@sbwalker Yep! I have updated the PR

@sbwalker
Copy link
Member

sbwalker commented Aug 8, 2023

@leigh-pointer I just realized that the behavior I described above was not actually working in 4.0.1 - it was fixed in #3119 (yesterday)

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.

2 participants