fistlabs / finger Goto Github PK

Rule pattern should support query arguments declaration.

Every query argument may be optional or required.

One optional argument:

/?foo

One required argument:

/&foo

Query declaration should support any number of argument declarations:

/&foo&bar?baz?zot

Query declaration should support same argument declaration with different options

/&foo?foo

Query declaration should support quantifiers for arguments

/&foo+?bar+

Query arguments declarations should support same syntax as path arguments

/&Number:id?{\\w+}:tag+

Query declaration should can be omitted and all the arguments should be parsed

/?

like

/?sort[type]=some-type&sort[order]=asc

It might be handy to pass paths to url.format

example

/<page[type]>/post/<page[postId]>/

support the ability to create different routes for patterns / and /?foo=bar
it should affect to matching result: url query must contain all the pattern query parameters

• #10
• #11
• #12
• #13
• #14
• #15
• #16
• #18
• #20

/news/(<postId>/)?feedId?*

?* - should extend args with all extra parsed query arguments when matching and should extendquerystring with all extra passed values when building

/news/?*

Handy to provide back compatibility with 0.3 but hard to implement and could make matching and building a little bit slower

• Implement query parameters describing #87
• Make Router main package module. Expose Rule, Matcher as static members of Router, document Router
• Support common types #89

Number \d+
Alnum \w+
Path [^?&]+?
String [\s\S]+
Ident [a-zA-Z]\w*(?:-[a-zA-Z]\w*)*
Segment [^?&]+?

Во избежание недоразумений. Path и Query кодируются похожим образом, но некоторые части урла кодируются по-другому