[feature/xcstrings-build-normalization] Normalize xcstrings on every build #131
Conversation
This file contains 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
|
|
felix-schwarz
changed the title
|
we might want to add this as a ci check to make sure only properly formatted xcstrings files are committed. |
- ocstringstool: update to normalize xcstrings - ownCloudSDK.xcodeproj: remove normalization step - pull-transifex.yml: integrate updated ocstringstool
|
Superseded by #134 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
Adds a xcstrings normalization build step that normalizes the
xcstringsfiles on every build. Since Xcode's format slightly diverges from the normalized version created byjq, this normalization step seeks to avoid large diffs for what is effectively few or no changes.