Closed jerelmiller closed 4 months ago
Latest commit: 2cb5a8c8bd1c3af5a25e16ed1bfbf44866d5329c
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
Click here to learn what changesets are, and how to add one.
Click here if you're a maintainer who wants to add a changeset to this PR
The interaction between the client and the cache to determine whether the user has enabled data masking is very awkward. The current implementation relies on the client setting a property on the cache after the cache was created. While this works, this feels a bit leaky.
This change removes the property from the cache object and instead does the check in
ObservableQuery
itself before callingcache.maskDocument
which is a bit more natural sinceObservableQuery
has access to this value.