chore: Place pagefind assets next to other assets#883
Merged
Conversation
This allows us to match requests to pagefind URLs using our asset rate limiting rule instead of the catch-all rule. The pagefind assets were previously /pagefind. Now, they are placed alongside other assets under /_/pagefind.
✅ Deploy Preview for stackable-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
This file contains hidden or 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
2 participants
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.
Note
Wait for merge until the submodule has been updated.
This allows us to match requests to pagefind URLs using our asset rate limiting rule instead of the catch-all rule. The pagefind assets were previously /pagefind. Now, they are placed alongside other assets under /_/pagefind.