Remove volatile computed properties #207
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.
Volatile computed properties are deprecated (https://deprecations-app-prod.herokuapp.com/deprecations/v3.x/#toc_computed-property-volatile). These were only used internally, so they can safely be converted to methods.
These could also be implemented using
Object.defineProperty
to define ES5 getters, and I'm happy to do that if preferred, but I don't see what that extra code complexity buys us over just making them methods.