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
A lot of web frameworks have a concept of "routes" which allows you to define a set of URLs that your app understands, and generates the code to parse the routes in a router, and code to generate the routes from their parameters, for use in in-app navigation/URL generation.
It would be cool to have the ability to configure routes, and have the route parsing/generation functions fall out of that. This could either be a data structure with functions that know how to operate on that structure, or it could be a macro. GADTs feel like they could be relevant for tagging route data types somehow, but not sure if that's a good idea.
The text was updated successfully, but these errors were encountered:
A lot of web frameworks have a concept of "routes" which allows you to define a set of URLs that your app understands, and generates the code to parse the routes in a router, and code to generate the routes from their parameters, for use in in-app navigation/URL generation.
It would be cool to have the ability to configure routes, and have the route parsing/generation functions fall out of that. This could either be a data structure with functions that know how to operate on that structure, or it could be a macro. GADTs feel like they could be relevant for tagging route data types somehow, but not sure if that's a good idea.
The text was updated successfully, but these errors were encountered: