feat(v7): stabilize advanced routing#13983
Conversation
✅ Deploy Preview for astro-docs-2 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Lunaria Status Overview🌕 This pull request will trigger status changes. Learn moreBy default, every PR changing files present in the Lunaria configuration's You can change this by adding one of the keywords present in the Tracked Files
Warnings reference
|
|
Thanks @matthewp, done in f60c839! Reposting my only doubt here:
What do you think about I mean, when using
|
|
We shouldn't document AstroFetchState, that only exists for types. From the user's perspective it's just the |
|
Changes to the upgrade guide look great, thanks! |

Description (required)
Updates docs to stabilize advanced routing. Kinda supersedes #13944
src/app.tsrenamingexperimental-flags/advanced-routingcontents toreferences/modules/astro-fetch.mdx(new),references/modules/astro-hono.mdx(new),guides/routing.mdx, and/en/guides/integrations-guide/cloudflare.mdx.experimental-flags/advanced-routingtranslationsMost of the content comes from
experimental-flags/advanced-routing. But I have tweaked/reworded/reorganized some parts for better integration (ie. a more guide/reference style).Happy to discuss about the organization (e.g. do we want advanced routing to be more visible?). And maybe this requires more changes, I haven't checked everything yet (e.g. Routing reference says "There is no separate routing configuration in Astro." which sounds maybe a bit outdated now).
Questions:
AstroFetchStatebe documented? I can see this is the public contract / this matches what we describe underFetchState. But doingconst state = new FetchState();returnsFetchState(the whole object, with private things) notAstroFetchState. So, I'm not sure how to integrate that.Related issues & labels (optional)
For Astro version:
7.0. See astro PR #16877.