Hubert Drecker

Just to be sure, the current implementation of `select` and `expand` works according to the spec. The generated OData client will only request the stuff which was specified in the...

Hi @assertnotnull, yeah, that hasn't been implemented as of now. And it probably will take a while to circle back to this issue. As workaround you're able to explicitly provide...

Yes, this feature is still wanted and help is always welcome!

Hi @brandonryan, wow, looks great at first glance. One note: Reversed operations like `unselect`, `clearSelection` and `unexpand` are not needed (see [stay fluent](https://odata2ts.github.io/docs/query-builder/querying#stay-fluent)). I will need some time though to...

To expand on the example model itself, a full-fledged example could look like this: * `string` * `number` * `Array` * `EnumType` * `Array` * `ComplexType` * `Array` * `EntityType`...

Hi @brandonryan, thanks so much for the effort already! I really need some time to delve into the coding and make up my mind how this can be reconciled with...

## TODO List for V3 Support This comment is a **Work In Progress** thing for now. V3 support requires a thorough reading of the V3 spec. ### To Improve -...

Hi @szarcensky, in the [original discussion](https://github.com/odata2ts/odata2ts/discussions/217#discussioncomment-7148647) you stated: > my service is v3. The class structure is expecting the response in the format `response.data.d.results` but what's coming back from the...

Hi @szarcensky, ok, [this article sheds some light on what is happening](https://learn.microsoft.com/en-us/aspnet/web-api/overview/odata-support-in-aspnet-web-api/odata-v3/creating-an-odata-endpoint#formats): > OData supports several serialization formats: > * Atom Pub (XML) > * JSON "light" (introduced in OData...

Hi @Shmookoff, what's your use case: model generation or full odata client?