Currently only Next.js is end-to-end tested. In order to ensure the same high standards of quality for other adapters, they should get the same treatment.
There may be a lot of overlap for testing the basic functionality common to each framework, and having to maintain those test pages & fixtures might become painful. Suggestions welcome!
CI Layout
There would be many levels of CI that need to be decoupled to make it all efficient (ie: running jobs in parallel).
Building & unit-testing the library, before anything else. No need to run e2e if this breaks for some reason.
Fan out by framework
a. Next.js (all supported versions, with variants)
b. Remix (do we need variants?)
c. React Router
d. React SPA
We can probably remove the ISR invalidation method once we move the docs to Next 15 and "use cache". What's the cache cascade going to look like if the top-level page is static but contains cacheLife / cacheTag elements?
Currently only Next.js is end-to-end tested. In order to ensure the same high standards of quality for other adapters, they should get the same treatment.
There may be a lot of overlap for testing the basic functionality common to each framework, and having to maintain those test pages & fixtures might become painful. Suggestions welcome!
CI Layout
There would be many levels of CI that need to be decoupled to make it all efficient (ie: running jobs in parallel).
We can probably remove the ISR invalidation method once we move the docs to Next 15 and
"use cache"
. What's the cache cascade going to look like if the top-level page is static but contains cacheLife / cacheTag elements?