OData APIExplorer route template with KeyAsSegment should not quote strings

[Rob4001]

Related to #502
Paths being generated for our Swagger docs are including paths such as /API/v1/Resource/'{key}'/SubResource

While the server side routes are /API/v1/Resource/{key}/SubResource

Creating the issue where swagger "try it out" includes the quotes which will be passed to the controller as "'key'".

It looks like the ODataRouteBuilder has the functionality to bypass quotation when KeyAsSegment is set to true but is not passing through to ExpandParameterTemplate when only a single (or first) key

Thanks in advance, really appreciate the library

[commonsensesoftware]

Doh! Thought I fixed this. Looks like there are a couple of cases where the wrong overload is used. This should be a quick fix.

I've been trying to find a comprehensive breakdown of what the Key As Segment rules are, but I've never found them. Do you happen to know? I've mostly been going off of knowledge of the protocol and occassionally spelunking the OData source code.

Here's things I've been looking for:

• Are composite keys supported?
  • If so, how? /entity-set/{key1}/{key-n}?
• Do key segments never use OData URL encoding? (ex: string, GUID, binary, duration, geometry, geography, etc)
• Do the Key As Segment rules apply to non-entity sets, such as unbound actions or functions?

If you happen to have or know of a sample project that uses this setup, that would be useful too. I feel like every time I've tried to set it up myself it ends up not working as expected. Thanks.

[commonsensesoftware]

FYI ... the patch for this has been published.