DapperLib / DapperLib/Dapper

Multi Mapping for QueryUnbufferedAsync?

Open
#1,942 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C#
Stars
18.4k
Forks
3.7k
Avg merge
5h 8m
Merged PRs (30d)
1

Description

The method
public static Task<IEnumerable<TReturn>> QueryAsync<TFirst, TSecond, TReturn>(this IDbConnection cnn, string sql, Func<TFirst, TSecond, TReturn> map, object param = null, IDbTransaction transaction = null, bool buffered = true, string splitOn = "Id", int? commandTimeout = null, CommandType? commandType = null)
seems to have no equivalent with a QueryUnbufferedAsync name. Is this an oversight or intentionally not implemented?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the QueryAsync<TFirst, TSecond, TReturn> overload in the Dapper source and checking whether a QueryUnbufferedAsync counterpart exists for other mappings. Determine whether the missing overload is intentional or should be added, then verify the expected behavior with the relevant query-mapping tests; done means the API decision is clear and covered by tests if changed.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp, sql
Domain
api, database
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.