JuncalLP

Hi there @texttechne Ideal solution IMHO would be Approach 1. Approach 2 would be a nice workaround and a way for the library to offer more flexibility, for sure, but.....

@texttechne if including an entity would make odata2ts navigate relationships and include dependencies the result would be ¿the same? It's the same behavior from [ODataConventionModelBuilder](https://learn.microsoft.com/en-us/odata/webapi/convention-model-builder) that got every EntityType included...

That's greater than Number.MAX_SAFE_INTEGER, so I guess kinda expected?