Allow setting options before initialising the Pagefind search JS #400
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.
Addresses #129
Adds a new step to the flow of initializing Pagefind via the JavaScript API:
Previously the import itself would init and start loading assets, which meant the
options()
call could not affect this by changing thebasePath
orlanguage
.Now, Pagefind will initialize when
init()
is called, or when any call to search or filters is made. As such, this change won't break any existing implementations, but may delay the loading of Pagefind until a search is made.