Treat empty filters {} the same as None. #514
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
I have been running benchmarks for synced collections (#484) and noticed that my project was loading state point data even when not requested.
I traced this down to the recent changes in #332 that changed the default
filter
behavior fromNone
to{}
. This prevented some of the "fast path" checks from triggering, and caused a full index for the project to be constructed.Motivation and Context
Bug fix.
I don't know how to test this effectively, because it only affects internal APIs and performance, not correctness.
Types of Changes
1The change breaks (or has the potential to break) existing functionality.
Checklist:
If necessary: