DapperLib / DapperLib/Dapper

QueryAsync with custom mapping AND CancellationToken

Open
#2,125 7 comments 0 reactions 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

I want to use QueryAsync with multiple types mapped onto a single return type WITH a cancellation token but none of the QueryAsync functions allow for that.

My current solution is to use the private MultiMapAsync method but this is not ideal and I don't know what the right solution to this would be but I'd like to talk about it and if you're down I can make a pull request.

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 comparing the public QueryAsync overloads with the private MultiMapAsync method mentioned in the issue, then review how cancellation tokens are handled by existing overloads. Done means the supported public API can combine custom multi-mapping with a CancellationToken without requiring callers to use a private method.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
backend-api-design, databases
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.