We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
As mention in #1
Add a new API for filtering out the unwanted parameters:
in the config file .next-boost.js, if we add the following config:
.next-boost.js
module.exports = { ... paramFilter: (p) => { p === 'fbclid' || p.startsWith('utm_') ? false : true }, }
In paramFilter, we just return true for the params you want to keep and false for those you want to remove.
paramFilter
true
false
With the filter, /path?fbclid=abc will be transformed to /path before searching the cache.
/path?fbclid=abc
/path
Before:
No paramFilter
After:
with paramFilter:
(p) => !p.startsWith('utm_')
The text was updated successfully, but these errors were encountered:
Add param filter to solve #5
97d1e76
551f19a
No branches or pull requests
Plan
As mention in #1
Add a new API for filtering out the unwanted parameters:
in the config file
.next-boost.js
, if we add the following config:In
paramFilter
, we just returntrue
for the params you want to keep andfalse
for those you want to remove.With the filter,
/path?fbclid=abc
will be transformed to/path
before searching the cache.Effect
Before:
No
paramFilter
After:
with
paramFilter
:The text was updated successfully, but these errors were encountered: