Bojan Bogdanovic
Bojan Bogdanovic
Bump! Merge conflict is resolved.
I think this is the same issue as: #788
Well we are currently on 1.6, but we are migrating soon to 2.0, there aren’t really BC’s regarding this cache tag invalidation logic. We are using JSON:API to build the...
I have pushed to code, so please take a look ;) Some small notes: - You need to add "X-NextJS-Site" header in the DrupalClient (on the frontend), so that the...
Hi @backlineint, Thanks for your input! > This implementation is for Next.js' Pages Router, which technically only has native support for invalidating by path. Your implementation bridges that using this...
Not that I'm aware of. For me there is a specific case for the trailing space. I would remove the trim function, which is in my opinion cleaner and gives...
One phpcs error left on CacheTag.php.
@minnur Yes this is possible, the only concern that I have is that the cache tags tables will grow, due the fact it will register more cache tags dependencies. The...
I’ve encountered the same issue. I tried using a custom fetcher on the Drupal client and setting `next` with a `revalidate` value matching the access token expiration time on the...
The no-store approach I previously suggested is a no-go because it breaks SSG. The suggestion from @boazpoolman to add a timestamp URL query parameter to the fetch seems like a...