Core: Optimize storiesHash
by removing unused parameters
#11624
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.
Issue: #11618 #11229
What I did
storiesHash
is the manager-side version of the story store. Currently it's doing a bunch of unnecessary work merging story parameters up the hierarchy of stories/groups/roots, which can be slow for storybooks with large sets of parameters.With @ndelangen:
viewMode
anddocsOnly
parameters up the tree, as they are used in group nodesPerformance implications
We saw a minor perf improvement on
official-storybook
. We assume this would be more pronounced for a more parameter-heavy/deeply nested storybook:setStories
= 885mssetStories
= 640msHow to test
official-storybook
and verify