-
Notifications
You must be signed in to change notification settings - Fork 0
Use Cases
Is an action performed by an actor against a system; where the actor interacts through a user interface with the system and it processes the interaction information producing several results, some as an output (that uses to be delivered to the actor), some as a change of what is known as the internal state (what involves change of data stored and managed by the system) and some as the execution of tasks (what may involve calling external systems).
Astro conceives use cases as HTTP Requests made by the browser against an Astro application rendered "on-demand", so the "actor" will be in general terms, the end-user using the browser.
As a rule of thumb, Astro will focus in rendering Pages as the main result of the use case started by the actor.
In some other occasions, there won't be a render, cause the "actor" might be a Javascript code executed by the browser. When that happens Astro will focus in executing a Server Endpoint.
Are those use cases involving the execution of other minor (aka "SubUse Cases") ones, where the main process becomes the actor.
Happens whenever the browser navigates to a path in this project site domain which matches an Astro Page Route for current project.
In that case, the Authentication Middleware intercepts the request in order to check if the requested path matches a private route.