Add section for regex validation and for wildcards with suffix

README.md

@@ -113,10 +113,19 @@ Named parameters only match a single path segment:
 ```
 Pattern: /user/{user}
 
- /user/gordon              match
- /user/you                 match
- /user/gordon/profile      no match
- /user/                    no match
+ /user/gordon						match
+ /user/you							match
+ /user/gordon/profile				no match
+ /user/								no match
+
+Pattern with suffix: /user/{user}_admin
+
+ /user/gordon_admin					match
+ /user/you_admin					match
+ /user/you							no match
+ /user/gordon/profile				no match
+ /user/gordon_admin/profile			no match
+ /user/								no match
 ```
 
 **Note:** Since this router has only explicit matches, you can not register static routes and parameters for the same path segment. For example you can not register the patterns `/user/new` and `/user/{user}` for the same request method at the same time. The routing of different request methods is independent from each other.
@@ -125,6 +134,12 @@ Pattern: /user/{user}
 
 If you need define an optional parameters, add `?` at the end of param name. `{name?}`
 
+#### Regex validation
+
+If you need define a validation, you could use a custom regex for the paramater value, add `:<regex>` after the name. For example: `{name:[a-zA-Z){5}]}`.
+
+**_Optional paramters and regex validation are compatibles, only add `?` between the name and the regex. For example: `{name?:[a-zA-Z){5}]}`._**
+
 ### Catch-All parameters
 
 The second type are _catch-all_ parameters and have the form `{name:*}`.