URI Query Parameter names starting with "$" won't parse

[vzwick]

## SomeResource [/SomeResource{?$top}]

### SomeOperation [GET]

+ Parameters

    + $top = `15` (optional, int, `30`) ... The amount of rows to return.

throws a parse error:

Ignoring unrecognized list, expected parameter discussion, e.g. ' ... lorem ipsum'.

[vzwick]

It seems like this is closely related to #90

[zdne]

@vzwick

It seems like this is closely related to #90

Yes. However note $ is not allowed character for a variable name according to RFC6570 – http://tools.ietf.org/html/rfc6570#section-2.3

May I ask you where is this being used?

[vzwick]

@zdne - sure. The culprit is OData, where query string variables like $top, $skip and $filter were obviously considered a good idea.

Unfortunately, OData is baked into the ASP.NET Web API, so pretty much everyone stuck on the Microsoft ASP stack will be facing the same problem as I do.

[zdne]

Thanks!

Given the $ is unacceptable character in URI Template variable – what would be the best acceptable solution for you?

Is pct-encoding in the variable name in the URI Template bearable?

[vzwick]

@zdne yes, of course.

[zdne]

This is also related (duplicate) to #107

[zdne]

Please track this issue at #107