OData can be used now, no restriction. However, we can create an integration package to provide some base class and services to develop OData controllers easier (like did before for current aspnetboilerplate).
I added this to backlog.
Any news on this? I would like to use ABP.io as the back end of a Blazor App, powered by Syncfusion controls. These work best with remote data over OData.
Link: https://ej2.syncfusion.com/blazor/documentation/grid/data-binding/?no-cache=1#web-api
Haven't worked on this yet. And contribution is appreciated :)
Has to wait for https://github.com/OData/WebApi/issues/1748
in .Net Core 2.2, I used app.UseMvc and set
routes.EnableDependencyInjection();
routes.Select().Filter().Expand().MaxTop(null).OrderBy().Count();
through IRoutingBuilder extension methods.
Now, in .Net Core 3.0, when I use app.UseEndpoints, how can I do this for injecting ODataQueryOptions?
In other words, how to enable OData components on non-OData routes in .net core 3.0 Endpoints?
@MasiumDev
We should first wait for ODate to support net core 3.0.
https://github.com/abpframework/abp/issues/990#issuecomment-549988064
@MasiumDev
We should first wait for ODate to support net core 3.0.
#990 (comment)
Since version 7.3 has support for net core 3.1
Most helpful comment
OData can be used now, no restriction. However, we can create an integration package to provide some base class and services to develop OData controllers easier (like did before for current aspnetboilerplate).
I added this to backlog.