Allowing hyphens in Query Params

I have a query param that has a hyphen as the key. e.g. foo-bar, but dredd is throwing an error that it’s invalid.

For example:

## Things [/things{?widget-type}]

+ Parameters

      + `widget-type`: wonky (string)

But when I run dredd, I get:

error: Runtime compilation error:
 Failed to parse URI template: /things{?widget-type}
 Error: SyntaxError: Expected "(", "*", ",", ":", "}" or [a-zA-Z0-9_.%] but "-" found.
 on  > Things > widget-type
error: Error parsing ast to blueprint.

I haven’t see any specs that prohibit -

• rfc3986
• rfc6570
• Query_string

Looks like the source is https://github.com/grncdr/uri-template/issues/14

[T0nyACr0ntum]

@honzajavorek Thanks, for the help… I just tried to escape the value but not the key. Escaping on both sides works fine!

[armen-ch]

Sorry for activating this long ago closed discussion but it’s really important for integrating Dredd into our api validation process. We have dozens of microservices which have parameters which contain hyphens in their names and we can’t use Dredd because of this limitation. Btw swagger editor normally accepts those apis as completely valid schemas (screenshot is attached). I did some research and came across different articles in the internet which declare hyphen as a valid query parameter character and looks like it’s widely used, e.g. https://en.wikipedia.org/wiki/Query_string https://developers.google.com/maps/url-encoding https://www.oreilly.com/library/view/restful-web-services/9780596809140/ch04.html https://stackoverflow.com/questions/32348875/can-hyphens-be-used-in-query-string-values https://datatracker.ietf.org/doc/html/rfc3986#section-2.3

Moreover it is highly encouraged to use hyphens instead of underscores when designing URI : https://developers.google.com/search/docs/advanced/guidelines/url-structure#:~:text=We recommend that you use,( _ ) in your URLs

I understand that you are trying to stick with rfc6570 but probably few follow the rules. Is it possible to replace this exception with warning? Or may be add some option/config to switch between interpretation of this rule as warning or error?