chore!: properly add the removal of utils.global to the renamings file. #6204
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.
The basics
npm run format
andnpm run lint
The details
Resolves
N/A
Proposed Changes
This is clean up from #6120
Behavior Before Change
Before it was possible to access the global-this via
Blockly.utils.global
.Behavior After Change
Now the global-this should be accessed via
globalThis
Reason for Changes
Providing access to the global this is not Blockly's responsibility. And polyfills will make it accessible to Blockly's internal code.
Test Coverage
Tested that this renaming works by:
Blockly.utils.global
in it.Blockly.utils.global
was properly changed toglobalThis
Documentation
N/A
To Migrate
Rename all instances of
Blockly.utils.global
toglobalThis
. You can do this automatically using the blockly/migrate script.