Feasibility of OData with current Microsoft support/investment

Hello All,

From the commit activity it seems like @xuzhg has basically been working solo on this and the core library for some time. Some major breaking changes (like the routing changes) have been made with what seems like an "experimental" vibe, leading me to wonder how much investment Microsoft has made here. Some of the other issues like #109 which seems like it has been potentially around for a long time (and with tests commented out) also seem to support the idea that this initiative is not being adequately resourced.

With OData powering the Microsoft Graph we figured OData would be well supported and invested in by Microsoft, and I am just trying to bridge the gap between expectations (robust, battle tested libraries) and recent observations (poorly resourced, "fringe" product).

We would love to move forward with OData and are invested in it, however would like to get thoughts on:

1. Is this project adequately resourced on Microsoft's part?
2. What does Microsoft Graph use under the hood for OData support?
3. Looking forward, is it reasonable to continue building with OData or should we be switching to other options like graphql or Automapper type solutions?

I really do not know much about the project and so my perception here could be way off! Any guidance is appreciated!