OpenApiQuery
OpenApiQuery copied to clipboard
Danielku15
OData based query language for your ASP.net core APIs
The OpenAPI specification provided by NSwag should be used for serializing/deserializing types as per definition there. Also the query parameters should be documented accordingly.
I am very interested in this project, as it covers exactly what I need from oData without all the extra clutter I do not need. With the current status and...
The error handling and reporting to API clients regarding malformed queries is quite poort and should be improved.
The OData standard defines the OData Error response. It is maybe worth having a opt-in consistent error response writing.
At many places we still use raw reflection. We must consider caching them as compiled lambdas for optimal performance.
Devs might want to change some behaviors, We must decide which parts of the framework are public and extensible.
Those variables are often needed in queries: $it, $root, $this
OData allows addressing the count of collections via property/$count. This should be supported in queries. e.g. like `/users?$filter=trips/$count gt 10`
Spatial types are quite a nice feature of EF and should be supported in OpenApiQuery.
Support data aggregation like described in http://docs.oasis-open.org/odata/odata-data-aggregation-ext/v4.0/cs01/odata-data-aggregation-ext-v4.0-cs01.html
Metadata
Owner
Metadata
OData based query language for your ASP.net core APIs