Closed
Description
Discussion on how augment route definition (regexp, optional params, constraints,...)
We should agree in the following, in no particular order:
- Optional parameters
- Type definition (restrict to string, to integers, paths, list). Especially important is the path, as it allows using parameters that contain slashes.
- Min/max length
- Regexp syntax
We could use the following pull-requests as a guide:
- Pull Request $route should allow regexps params angular/angular.js#918: $route should allow regexps params
- Pull Request feat($route): regexp support for $route params angular/angular.js#972: feat($route): regexp support for $route params
- Pull Request fix($resource) Route constructor, updated RegExp angular/angular.js#1402 fix($resource) Route constructor, updated RegExp
- Pull Request feat(routeProvider): Add support to catch-all parameters in routes angular/angular.js#1560: feat(routeProvider): Add support to catch-all parameters in routes
- Pull Request Improved Angular routing in a backwards compatible way. angular/angular.js#1634: Improved Angular routing in a backwards compatible way.
- And of course, the discussion on Design #1
Metadata
Metadata
Assignees
Labels
No labels