Repository navigation
Cupertino localization step 1.5: fix a resource mismatch in cupertino_en.arb - #29821
Merged
Merged
Conversation
goderbauer
added
framework
HansMuller
approved these changes
Mar 27, 2019
HansMuller
left a comment
HansMuller
left a comment
Contributor
There was a problem hiding this comment.
Eventually this kind of thing should be caught by the validateLocalizations() step in dev/tools/gen_localizations.dart (right?)
Member
Author
|
It will. Just at this point, there isn't enough stuff in gen_localizations to know this file existed yet. It's also how I caught this thing later :D |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Fix a typo in cupertino_en.arb
Related Issues
#13452
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes (
[x]). This will ensure a smooth and quick review process.///).flutter analyze --flutter-repo) does not report any problems on my PR.Breaking Change
Does your PR require Flutter developers to manually update their apps to accommodate your change?