-
Notifications
You must be signed in to change notification settings - Fork 30
feat(website): AllowPageCache section for CMS-only pages #1649
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
Closed
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,25 @@ | ||
| import { PAGE_CACHE_ALLOWED_KEY } from "@deco/deco/blocks"; | ||
| import type { AppContext } from "../../mod.ts"; | ||
|
|
||
| /** | ||
| * Opts the current page into CDN page caching. | ||
| * | ||
| * The runtime only emits a public `Cache-Control` when some middleware marks | ||
| * the request as safe to cache (see `PAGE_CACHE_ALLOWED_KEY`). Commerce apps | ||
| * like VTEX do this from their middleware, but CMS-only pages (e.g. a home | ||
| * built purely from `website` sections, with no commerce loader) never opt in | ||
| * and therefore stay uncached. | ||
| * | ||
| * Drop this section on such a page to make it cacheable. It is still guarded by | ||
| * the runtime: if a foreign `Set-Cookie` is present, or another block on the | ||
| * same page marks the response `no-store`, that decision wins. | ||
| */ | ||
| export const loader = (_props: unknown, _req: Request, ctx: AppContext) => { | ||
| ctx.bag?.set(PAGE_CACHE_ALLOWED_KEY, true); | ||
| return {}; | ||
| }; | ||
|
|
||
| // Renders nothing — this section exists only to opt the page into caching. | ||
| export default function AllowPageCache() { | ||
| return null; | ||
| } | ||
Oops, something went wrong.
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.
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.
P2: The loader uses
ctx.bag?.set(...), which will silently do nothing ifbagis undefined — but setting this key is the sole purpose of the section, so a silent no-op means the page stays uncached with no indication why. The VTEX middleware this PR mirrors uses non-optionalctx.bag.set(...); consider matching that or adding a warning if bag is missing.Prompt for AI agents