Why only QueryAsync method have mulit mapping method overload with CommandDefinition
Open
Nobody has claimed this yet.
area:api
- Dominant language
- C#
- Stars
- 18.4k
- Forks
- 3.7k
- Avg merge
- 5h 8m
- Merged PRs (30d)
- 1
Description
The QueryAsync method have mulit mapping method overload with CommandDefinition
public static Task<IEnumerable<TReturn>> QueryAsync<TFirst,..., TReturn>(this IDbConnection cnn, CommandDefinition command, Func<TFirst,...TReturn> map, string splitOn = "Id");
But the Query method has no CommandDefinition method overload. what is the purpose for this design ?
dapper version = 1.50.2
<?xml version="1.0" encoding="utf-8"?>
<packages>
<package id="Dapper" version="1.50.2" targetFramework="net461" />
</packages>
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.
Research direction
Start by locating the public Query and QueryAsync overload declarations and compare their CommandDefinition and multi-mapping signatures. Determine whether the missing synchronous overload is intentional or should be treated as API parity work; completion requires an agreed design and corresponding project validation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100