Path segments with a period only generate a property using the final part of the segment after the dot

[darrelmiller]

Using this description https://raw.githubusercontent.com/nytimes/public_api_specs/master/movie_reviews/movie_reviews_v2.json

it generates code that looks like this

var review = await reviewClient.Reviews.Json.GetAsync(rc => rc.QueryParameters.Query = movieName);

The API actually looks like this

Ideally it would be reviewClient.Reviews.SearchJson

I'm not sure how to handle OData actions and functions that are fully qualified with a namespace.

[baywet]

IMHO having a file extension in an API path is just bad design: I kind of locks the client in a single content type, making the accept header useless and any evolution to support future formats a breaking change.

That being said, we could "patch that" without breaking the OData namespace segmenting by simply stripping a few known extensions from the fluent API segmenting. (json, csv, txt, yaml, yml...)

The code path would then become

var review = await reviewClient.Reviews.GetAsync(rc => rc.QueryParameters.Query = movieName);

Thoughts?

[darrelmiller]

IMHO having a file extension in an API path is just bad design

Roy Fielding disagrees :-) So we might want to account for the possibility.

Yeah, I think stripping a set of known extensions is a reasonable compromise.