Use to-be-closed variables to scope WML variables in tag definitions #5536
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
Please add a WML-based unit test for this. |
github-actions
bot
added
the
Unit Tests
Done. |
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.
With this you no longer have to worry about forgetting to end the variable scope - Lua will do it for you automatically. This is a PR because I've only done a basic smoke test (making sure there are no errors when starting a game; for this test I chose Aethermaw). I didn't confirm that the variable is correctly set and unset, though I have no reason to expect it wouldn't be; I did do some testing to verify how to-be-closed variables work.