Convert the BasePreferences
class to use private fields
#14665
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.
Convert the
BasePreferences
class to use private fieldsGiven that none of these fields were ever intended to be accessed directly from the outside, since that will lead to inconsistent/broken state, we can use modern ECMAScript features to ensure that they are indeed private.
Revert Preferences to their previous values, when writing to storage failed
This patch fixes an old inconsistency, when using
BasePreferences.{reset, set}
, where the internal Preference values would be kept even if writing them to storage failed.