Convert Filter resolution from property to accessor #7769
Merged
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.
Description of change
This PR is an attempt to fix this issue that I've had with the PIXI Advanced Blur Filter (documented here: pixijs/filters#301). I describe the issue in detail there, but here's a short summary:
Filter
has a public property namedresolution
.AdvancedBloomFilter
overrides this property with an accessor namedresolution
.AdvancedBloomFilter
maintains a private_resolution
property which is set by this accessor (along with some other side-effects, which seems to be the whole purpose of using an accessor instead of a property).However, as of microsoft/TypeScript#37894,
tsc
now treats overriding a property with an accessor as an error.This PR converts the definition of
resolution
in the baseFilter
class to an accessor to avoid this error.Pre-Merge Checklist
npm run lint
)npm run test
)