-
Notifications
You must be signed in to change notification settings - Fork 89
test: loose some assertions for fallback: true e2e tests to allow nonbreaking next@canary changes #2976
New issue
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
Conversation
… breaking next@canary changes
if (!fallbackWasServed) { | ||
expect(headers1['netlify-cache-tag']).toBe(`_n_t_${encodeURI(pagePath).toLowerCase()}`) | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fallback does get cache tag with newest canary, but as long as it's not cacheable, we don't actually care about cache tag
Just note that same change is applied 3 times in this PR for variants of the similar test/fixture, but will just comment on first case
📊 Package size report No changes
Unchanged files
🤖 This report was automatically generated by pkg-size-action |
nextVersionSatisfies('>=15.4.0-canary.95') | ||
? `private, no-cache, no-store, max-age=0, must-revalidate, durable` | ||
: undefined |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Both of those mean "no-cache" in practice so those are generally the same in fact that fallback should not be cached
Just note that same change is applied 3 times in this PR for variants of the similar test/fixture, but will just comment on first case
Description
Follow up to #2974 that adjust assertions for currently failing tests now that
fallback: true
cache-control was fixed in vercel/next.js#80865