| UriTemplateMatch Method |
Overload List| Name | Description | |
|---|---|---|
 | Match(Uri) |
Attempts to match a Uri to a UriTemplate.
|
| Match(Uri, ICollectionString) |
Attempts to match a Uri to a UriTemplate.
|
| Match(Uri, Uri) |
Attempts to match a Uri to a UriTemplate.
|
| Match(Uri, ICollectionString, ICollectionString) |
Attempts to match a Uri to a UriTemplate.
|
| Match(Uri, ICollectionString, ICollectionString, ICollectionString) |
Attempts to match a Uri to a UriTemplate.
|
RemarksThere are several limitations in the current implementation of this operation.
- If more than one assignment of values to variables exists which is capable of producing the candidate URI through the BindByName Overload operation, it is unspecified which assignment of values is chosen.
- Simple string values will always be returned as a String. Associative array values will always be returned as an IListT whose values are of type String. Associative map values will always be returned as an IDictionaryTKey, TValue whose keys and values are of type String. No other deserialization or coercion of values is performed by this library.
The matching algorithm prefers to use simple string values for all variables not explicitly listed in arrayVariables and/or mapVariables. Any variable listed in either of these parameters will not be considered for matching as a simple string. If no assignment of values to variables is possible using this choice, one or more variables may be treated as associative arrays and/or maps in order to produce a successful assignment. The exception to this rule is compound template variables (which use the explode modifier); these variables prefer to match as arrays instead of simple strings, even if the result produces an array containing exactly one string. If a variable appears in both arrayVariables and mapVariables and the result successfully matches using both options, it is unspecified which one will be returned.
See Also