rlang Thu, 12 May 2022 12:22:33 +0000
Modified page: https://wiki.horde.org/Doc/Dev/Bootstrap
New Revision: 3
Change log: more random detail.
@@ -71,6 +71,14 @@
- But we do not need heavy weight app init upfront.
- For routing setup, we do not care if the app in question is
disabled, inaccessible for the current credentials or anything. This
should be handled by some middleware.
- Each app/service has its endpoint, identifying a first routing
level and at least some registry-defined routes for URI generation
(js, themes, templates, appwebroot)
- We want to be able to generate routes towards other apps inside
this installation.
-
+- nested route groups can be resolved to one single set of combined routes.
+- nested route groups can have default middleware stacks at each
level. These can be merged to a single middleware stack, including the
route's handler, middleware or stack
+- nested route groups can have a catchall on each level.
+- How to attach / autogenerate useful API docs (like openapi) from
routing information?
+- Are verbs part of the routing or should they be filtered by a middleware?
+- URI parameter constraints.
+- Collecting the routes into one consumable RoutesCollection should
be separate from consuming the RoutesCollection. Collect at
install/config time and save the result.
+- Routes Matching should produce a MatchedRoute exposing useful
information but should not call/dispatch the resulting stack.
+- The router must allow to pass through some information it is not
interested in by itself or does not recognize
--
commits mailing list
Frequently Asked Questions: http://wiki.horde.org/FAQ
To unsubscribe, mail: [email protected]
