You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a follow up to the discussion in #763 and #797
Similar to the module's path based revalidation, we should update the module to call our revalidation endpoint for the app router's revalidation by tag.
Describe the solution you'd like
For a next.js site (the config entity) we'd need to add an option under on-demand revalidation to select if we should invalidate by path, or by tag.
** Is there a real-world use case for needing both? That would complicate this feature quite a bit.
modules/next/modules/next_extras/src/NextCacheInvalidator.php will need new getTagsToInvalidate and invalidateTags methods.
** The invalidateTags method will make an API call to the revalidation endpoint, and pass a comma separated list of all cache tags using the tags parameter. (Updates to FE API route are outlined here: feat(next-drupal): next revalidate options #784)
invalidateEntity will need to add conditional logic to check for the invalidation type and adjust accordingly.
Describe alternatives you've considered
A page router based approach was implemented here: #797
The text was updated successfully, but these errors were encountered:
Package
next (Drupal module)
Describe the feature request
This is a follow up to the discussion in #763 and #797
Similar to the module's path based revalidation, we should update the module to call our revalidation endpoint for the app router's revalidation by tag.
Describe the solution you'd like
** Is there a real-world use case for needing both? That would complicate this feature quite a bit.
** The invalidateTags method will make an API call to the revalidation endpoint, and pass a comma separated list of all cache tags using the
tags
parameter. (Updates to FE API route are outlined here: feat(next-drupal): next revalidate options #784)Describe alternatives you've considered
A page router based approach was implemented here: #797
The text was updated successfully, but these errors were encountered: