fix!: remove backwards compatible get and set accessors #6203
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
Removes some get and set accessors (most of which were deprecated).
Behavior Before Change
These accessors were available.
Behavior After Change
These accessor are not available.
Reason for Changes
As we move to typescript, it's no longer possible to provide accessors directly on the exports object, so these have to be removed.
Test Coverage
N/A
How to Migrate
You can run the blockly/migrate script to automatically perform renamings in your files. If you are setting any of these values, you may need to do some manual edits to properly call the setter function.