de-duplicate the search index #2425
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Currently, the search index is duplicated in
searchindex.jsandsearchindex.json. It seems the reason for the duplication is that the.jsonallows for async loading viafetch()and the.jsprovides a fallback in case CORS causes issues with thefetch().The problem with having the duplicated index is that for large books, the index becomes quite large (2.5MB for my company's book!). It would be nice if the index didn't have to be duplicated.
This PR removes
searchindex.jsonfrom the site output. It replicates the async functionality by reading in thesearchindex.jsfile and parsing out the JSON within. The fallback remains unchanged.