BUG - Cannot map query result to object?
Open
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 18.4k
- Forks
- 3.7k
- Avg merge
- 5h 8m
- Merged PRs (30d)
- 1
Description
Dapper 2.0.35 in a .NET Core 3.1 console application,
https://stackoverflow.com/questions/64286917/how-can-i-map-a-dapper-queryfirst-to-a-class
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 reviewing the linked Stack Overflow question and reproducing the reported mapping behavior with Dapper 2.0.35 in a .NET Core 3.1 console application. Clarify the expected query-to-object result, then identify the affected Dapper entry point and add a regression test demonstrating the completed behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- database
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100