DapperLib / DapperLib/Dapper.Contrib
Dapper.Contrib does not respect SqlMapper.TypeMaps
Open
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 293
- Forks
- 109
- PR merge metrics
- No merged PRs in 30d
Description
The Dapper.Contrib does not use the ITypeMap instances set for mapping database table column names to POCO property names. Generated SQL statements therefore are wrong when using a POCO with property names not identical to database columns.
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 tracing Dapper.Contrib's generated SQL and how SqlMapper.TypeMaps are currently handled. Done means POCOs with property names that differ from database columns produce correct SQL using their configured ITypeMap instances; add or update coverage for that mapping case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- backend, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100