Should display query string parameters not described by the EDM model or in the ODataRoute about swashbuckle.odata HOT 7 CLOSED

@jondavis-ineight Can you please provide a sample ODataConfig for this? I.e., your ODataConventionModelBuilder configuration? Not sure at this point why this would be happening...

from swashbuckle.odata.

It's just

var builder = new ODataConventionModelBuilder { Namespace = "Default" };
builder.EntitySet<Foobar>("Foobars");
config.MapODataServiceRoute("odata", "odata", builder.GetEdmModel());

from swashbuckle.odata.

Researching...

from swashbuckle.odata.

Just curious, but wouldn't that end up being two separate routes? Following
the standard conventions set out by the convention model builder and
examples from Microsoft, shouldn't you have two methods on your controller?
One that takes zero parameters, and one that takes a key?

It seems like that would be the "correct" approach.

In your case, wouldn't it be better to simply set a parameter like this in
the query string?
On Fri, Jan 29, 2016 at 6:05 PM Richard Beauchamp [email protected]
wrote:

Researching...

—
Reply to this email directly or view it on GitHub
#62 (comment)
.

from swashbuckle.odata.

Hey @jondavis-ineight Fix for this issue is available in v2.12.5. Give it a try and let me know if you find any issues. Thanks!

from swashbuckle.odata.

So sorry I haven't had the chance to respond sooner. This is awesome, thanks! I'll take a look at this soon!

from swashbuckle.odata.

That seems to work. Thanks!

from swashbuckle.odata.