Skip to content
This repository was archived by the owner on Apr 12, 2024. It is now read-only.
This repository was archived by the owner on Apr 12, 2024. It is now read-only.

$route should allow regexps params #918

Description

@vojtajina

things like: /some/:param ([0-9]*)

or allow list of values, eg. /some/:param where param can be one of ['one', 'two', 'three']

Check out server side frameworks and their routing.

Activity

  1. hkdobrev commented on Jul 19, 2012

    @hkdobrev
    Contributor

    +1

  2. zygimantas commented on Sep 26, 2012

    @zygimantas

    I would recommend /some/<param:[0-9]*> pattern.

  3. blainegarrett commented on Nov 18, 2012

    @blainegarrett

    +1
    Additionally, I'd like to be able to include slashes as valid strings in the match. This appears not to work currently.

  4. lrlopez commented on Nov 18, 2012

    @lrlopez
    Contributor

    @blainegarrett, you should have a look into PR #1560 as it allows matching arbitrary strings which also include slashes.

  5. petrovalex commented on Dec 2, 2012

    @petrovalex
    Contributor

    @blainegarrett I was able to include slashes as valid string in my implementation just by extending the $routeProvider.shortcuts with { "path": { regex: "[\w\/]+" } } and then specifying the constraint for the parameter to be path. actually, I have exposed this shortcuts object, so that it is configurable from outside

  6. lucsky commented on Jan 11, 2013

    @lucsky

    +1

  7. rzajac commented on Jan 21, 2013

    @rzajac

    +1

  8. danieljsinclair commented on May 3, 2013

    @danieljsinclair

    +1

  9. tahir-asadli commented on Jun 7, 2013

    @tahir-asadli

    +1

  10. atian25 commented on Jun 20, 2013

    @atian25

    when will this merge to master?

  11. btford commented on Aug 24, 2013

    @btford
    Contributor

    As part of our effort to clean out old issues, this issue is being automatically closed since it has been inactivite for over two months.

    Please try the newest versions of Angular (1.0.8 and 1.2.0-rc.1), and if the issue persists, comment below so we can discuss it.

    Thanks!

  12. sky-joaonabais commented on Apr 29, 2016

    @sky-joaonabais

    +1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions