Provide additional parameters to support provision of execution context to Load and LoadAsync
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
Start with the DataSourceLoader.Load and LoadAsync entry points and review the AutoMapper Queryable Extensions parameterization linked in the issue. Determine how an execution context should reach the projection while preserving the existing CustomAccessors and CustomFilters flow; done means both overloads support the requested runtime parameters.
Written by the indexing model from the issue text.
Description
Hi Aleksey
Statler here - you may remember me from such posts as
- https://github.com/DevExpress/DevExtreme.AspNet.Data/issues/367
- https://github.com/DevExpress/DevExtreme.AspNet.Data/issues/277
So, just when I thought I had every base covered, I have come across a new use case that I need to manage. I am hoping you can help me out here.
My case deals successfully with automapper projection by:
- Registering CustomAccessors automatically from the automapper config (https://github.com/DevExpress/DevExtreme.AspNet.Data/issues/367)
- Getting the IDs of all results from the Devexpress.AspNet.data expression compilation query
- Querying the base type for all ids in (2), and using ProjectTo
This all works really well for ProjectTo(Mapconfig)
Where I have come unstuck is the overload of ProjectTo(Mapconfig, MapParameter) (https://docs.automapper.org/en/stable/Queryable-Extensions.html#parameterization)
This enables the injection of runtime variables into the projection and is a case I can't see a way to resolve as it is not possible to provide context in the CustomAccessors or CustomFilters. Would you be open to modifying the signatures for these methods to support the provision of context via an additional parameter to DataSourceLoader.LoadAsync / DataSourceLoader.Load
- Dominant language
- C#
- Stars
- 165
- Forks
- 140
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 4
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from DevExpress/DevExtreme.AspNet.Data
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Dependency Dashboard Open
Difficulty 4/5 3-5 days Newbie friendliness 15/100
-
ES6 support Openenhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
has-workaround
Difficulty 3/5 1-2 days Newbie friendliness 38/100
DevExpress/DevExtreme.AspNet.Data#501 · 1 comment ·
All issues in DevExpress/DevExtreme.AspNet.Data
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
nightscout/nocturne#1425 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
RayWangQvQ/BiliBiliToolPro#1137 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100