Fix loading serialized index from sessionStorage #1579
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.
I noticed that lunr throws an error when it tries to load the serialized index from the
sessionStorage
. This causes the index to be generated upon each new search entry, which can have a performance impact for large projects.Lunr throws the error because
elixirTokenSplitter
added to the pipeline during the index creation but it isn't registered when the index is loaded from thesessionStorage
.The following error is thrown when searching: