You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As astro grows in popularity, it is being used for more and more use cases. One of these is multitenant websites where a tenant may be given a subdomain. This proposal introduces a powerful primitive that allows astro users to build websites with complex routing requirements. Rather than a limitation, file-based routing is now a sensible default!
Goals
Defuse.
Make it unnecessary to rely on implicit routing rules
Introduce framework-designed 404 and 500 pages
Make middleware run for requests that don't match a route (with framework-designed error pages)
Non-Goals
Reroute to an external service.
Support for functionPerRoute
The text was updated successfully, but these errors were encountered:
Should be possible to set in any way using an API not file based routing. Example Astro.set404Page(({ props, context }) => Astro.render("ErrorPage.astro", { props, context }))) to make 404 page. props is for SSG and SSR and context for only SSR.
Separate templating
Function like Astro.render("Page.astro", { props, context })) to output html anywhere even outside astro. You could use astro templates in other frameworks like express and use other templating engines in astro just like any SSR framework.
Summary
Programmatic control over routing.
Background & Motivation
As astro grows in popularity, it is being used for more and more use cases. One of these is multitenant websites where a tenant may be given a subdomain. This proposal introduces a powerful primitive that allows astro users to build websites with complex routing requirements. Rather than a limitation, file-based routing is now a sensible default!
Goals
Non-Goals
functionPerRoute
The text was updated successfully, but these errors were encountered: