Dapper custom TypeHandler SetValue not being called?
Open
Nobody has claimed this yet.
bug
needs-investigation
v3.0
- Dominant language
- C#
- Stars
- 18.4k
- Forks
- 3.7k
- Avg merge
- 5h 8m
- Merged PRs (30d)
- 1
Description
I have exactly the same problem as it is described here: http://stackoverflow.com/questions/28727962/dapper-custom-typehandler-setvalue-not-being-called
Update:
There is a second thread with the same problem: http://stackoverflow.com/questions/25568657/dapper-typehandler-setvalue-not-being-called?rq=1
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 reading the two linked Stack Overflow reports and tracing Dapper's custom TypeHandler handling. Reproduce the reported case where SetValue is not called, then verify that the handler is invoked for the relevant parameter and that the existing behavior is covered by a regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100