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
Xun's Page Router is inspired by Nextjs's Page Router. It is same as expo's as you mentioned. But there are 3 problems.
directory is used in layout setup and routing
override layout issue on page level
layout might be mixed when host precedence is there.
re 1st, he has to keep an eye on directory when developers define their API routing. Because there is a directory limitation on its html viewer from Page Router.
re 2nd, a workaround is required.
re 3rd, a workaround is required too.
In Xun's design pattern, Handler Routing is a first-class citizen. Developers should feel free to define their API routing, with the Page Router following suit as merely an HTML viewer.
This is why the <!--layout:xx--> marker is introduced, allowing developers the freedom to apply any pattern to their APIs.
Consider another approach for layout structure: https://docs.expo.dev/router/layouts Instead of parsing the marker at beginning of files
The text was updated successfully, but these errors were encountered: