feat(next-drupal): next revalidate options #784
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.
Adds next revalidate options to resource-methods and custom fetch.
This pull request is for: (mark with an "x")
examples/*
modules/next
packages/next-drupal
starters/basic-starter
starters/graphql-starter
starters/pages-starter
GitHub Issue: #761
Code changes need test coverage. If you don't know
how to make tests, check this box to ask for help.
Describe your changes
I've extended the custom
fetch
function to accept the next revalidation options.fetch("https://...", { next: { revalidate: false | 0 | number } })
fetch("https://...", { next: { tags: ['node:1', 'tag:2'] } })
I've added the
next
option to the following resource-methods:It might be necessary to add it to CRUD methods or others, but I'll wait for feedback first.
I've added some unitary tests as well but might need refinement.
Contribution
Sponsored by @brainsum