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

Require a culture-specific globalize resource to accompany globalize when required by the compiler #721

Merged
merged 10 commits into from
Jul 30, 2019

Conversation

cafour
Copy link
Contributor

@cafour cafour commented Jul 15, 2019

Fixes #694.

When ToString is called on a number in a binding, the compiler adds a property to remember to require the "globalize" resource. It didn't, however, require the current-culture-specific globalize to accompany it, which lead to problems like #694 (the FeatureSamples_Localization_Globalize sample).

This PR attempts to fix this problem by adding a new control called GlobalizeResource whose sole purpose is to call ResourceManager.AddCurrentCultureGlobalizationResource, and a new binding property with a visitor that adds this control to the resolved tree when required just like before.

@cafour cafour requested review from quigamdev and tomasherceg and removed request for quigamdev July 15, 2019 12:00
@exyi
Copy link
Member

exyi commented Jul 17, 2019

No more cleanup PRs today. Please revert that diff noise so I can do the code review.

@tomasherceg tomasherceg merged commit 00f40af into master Jul 30, 2019
@tomasherceg tomasherceg deleted the fix/culture-specific-globalize branch July 30, 2019 15:07
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.

Cannot read property "numberFormat" of null
3 participants