Use strict #4
Open
Use strict #4
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
To minimize the further diffs.
|
@TerrariaMods-Scratch, would you like accessibility fixes here, or in a stack? |
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.
Review commit by commit.
First commit uses a formatter over the codebase. My editor does it either way, and this way I don't ruin commit diffs, only PR diffs.
Second commit updates a comment.
Third commit adds pragmas to the top of files to use es5. No, not es6. Not es2025. es5. 😜 (only commit that might break anything, for which I added @ts-check, which thinks it should be fine)