Fix Carriage Return Issue When Uploading DB Fields to Translation.io #524
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
'fix/carriage-return-issue' branch is based off the previous branch 'fix/broken_db_fake_method_calls'
This commit does not change the behaviour of the app. Rather, the carriage-return-issue branch was merged into the broken_db_fake_method_calls branch.
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.
Fixes #523
Changes proposed in this PR:
\rissue that was occurring when syncing db values to translation.iofix/broken_db_fake_method_callsand adds one additional change via the following commit: ualbertalib/translation_io_rails@5fb2d5cGemfile.lockchanges are the result of runningbundle installafter replacing the translation target branch inGemfile