Ensure new if blocks translate properly when locales are changes#304
Merged
tracygardner merged 2 commits intoflipcomputing:mainfrom Feb 19, 2026
Merged
Conversation
so that they still include the newline at the end
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
I kept the hardcoded newline characters in the (updated, where needed)
CONTROLS_IF_MSG_ELSEstrings for now, since we still have several example projects that still use the old if blocks. When these old if block uses are removed, the hope is to remove the hardcodedCONTROLS_IF_MSG_ELSEstrings in the near future so that we no longer need to override the ones Blockly already provides for these locales.