DapperLib / DapperLib/Dapper.Contrib
Remove reference type constraint from Contrib extension methods
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 293
- Forks
- 109
- PR merge metrics
- No merged PRs in 30d
Description
Is there a reason why all Contrib extension methods have a constraint to reference types? The base Dapper extension methods don't have such constraints.
I agree that those generally make sense, but right now they prevent me from using Dapper Contrib because I need to implement a generic interface that doesn't specify any type constraints.
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
Inspect the Contrib extension methods and compare their generic constraints with the base Dapper extension methods. Determine which reference-type constraints block unconstrained generic interfaces; done means the relevant methods accept value types or unconstrained type parameters without breaking existing behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- database
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100