(graphcache) - Refactor SelectionIterator and clean up exports #1060
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.
Summary
These changes were initially started to remove obsolete exports from Graphcache. Previously we would expose some
data.ts
internals so they could be used externally, but since we forgot to exposeinitDataState
those exports wouldn't be of much use anyway. So instead we can reduce our exports to a minimum just to satisfy ourbenchmark
's needs.Also this made me search for some more bundlesize opportunities, and I found that a small
traversal
helper could be rewritten and the sharedSelectionIterator
could be optimised a little. This also gave us a small micro-benchmark performance bump, since it's a hotpath.Set of changes
noopDataState
,writeOptimistic
, andreserveLayer
from exportsgetFragments
utility inast/traversal.ts
makeSelectionIterator
to become nested if needed and remove intermediary iterator object