Goals

[OptimusCrime]

General

• Use FastRoute to parse the routes.
• Implement with "autoloading" and Composer.
• ExtJS and custom table, complete CMP in the manager interface.
• Have something like regex101.com's matching tester for routes.
• Have a method similar to Slim/Smarty forRoute or something.
• Sort the routes by priority.
• Make the routes handle contexts in a smart way.
• The routes should handle separate GET, PUT, POST etc requests (or all).
• Call a route directly to a snippet(?).

Parsing

• Support all the stuff FastRoute supports, e.g. blog/{id:\d}.
• Make it possible to match a resource's URL, e.g. [[~16]]/{page:\d}.
• Make it possible to match a resource's attributes, e.g. [[16=alias]].
• Make it possible to match context/system settings, e.g. [[~++start_page=alias]].
• Make it possible to match multiple attributes, e.g. [[16=alias|uri]].
• Make it possible to match a resource's template variable s, e.g. [[16=tv.my_tv_here]].
• Make it possible to match children (of variable depth?), e.g. [[~16]]/[[16~1{1}=id]]-[[16~1{1}=alias]].
• Routes should be mapped to a specific resource, OR as in the example above, the resource that matches.

[OptimusCrime]

Kan ikke bruke pipe. Vil ikke fungere når man lager en URL

[OptimusCrime]

Structure

• Parser (parses the textual string into a GenericRouter representation)
  • All todays code
• Represention (representation that can be dumped and imported as JSON that expresses the textual string)
  • Code related to the final parser representation
• Validator (validates the representation)
• Matcher (matches a representation with a resource from MODX)
• Generator (generates a URI for a textual expression called from a MODX snippet)