Skip to content
This repository has been archived by the owner on Sep 6, 2021. It is now read-only.

Add grunt task to check for correct nls keys #11299

Merged
merged 2 commits into from
Sep 17, 2015
Merged

Conversation

marcelgerber
Copy link
Contributor

This grunt task checks that all nls keys referenced in a nls file are actually present in the root file, too.
This will help us spot typos and the like.

I've dropped all the keys removed from the root file, but still present in some nls files.

@abose abose added this to the Release 1.5 milestone Jun 23, 2015
@abose
Copy link
Contributor

abose commented Sep 11, 2015

There are a lot of string deletions in this PR. Is that intended?

@marcelgerber
Copy link
Contributor Author

Yes, these are intended.
They are all strings that are no longer being used in Brackets.

@abose
Copy link
Contributor

abose commented Sep 15, 2015

Thanks. Could you update the pr resolving merge conflicts?

@marcelgerber
Copy link
Contributor Author

Ready.

@abose
Copy link
Contributor

abose commented Sep 16, 2015

Merge conflicts again 😅 probably due to all language pr merges for 1.5.

@marcelgerber marcelgerber force-pushed the marcel/grunt-nls-check branch 2 times, most recently from 9daee42 to 7bb6520 Compare September 16, 2015 17:29
@marcelgerber
Copy link
Contributor Author

@abose It's mergeable again.

}
});

if (encounteredErrors) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why not call done(encounteredErrors)?

abose added a commit that referenced this pull request Sep 17, 2015
Add grunt task to check for correct nls keys
@abose abose merged commit 2703195 into master Sep 17, 2015
@abose abose deleted the marcel/grunt-nls-check branch September 17, 2015 07:25
@abose
Copy link
Contributor

abose commented Sep 17, 2015

Merged.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants