DapperLib / DapperLib/DapperAOT
TypeHandler<T> not respected by DapperAOT source generator
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 472
- Forks
- 43
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 18
Description
Hello there,
I’ve noticed that custom SqlMapper.TypeHandler implementations are not picked up or respected by the DapperAOT source generator. This leads to incorrect or missing code generation for types that rely on TypeHandlers for serialization/deserialization.
Would love to know if there’s a workaround for now.
Thanks for all the work on DapperAOT
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
No file, test, entry point, or reproduction is named. Start by isolating a custom SqlMapper.TypeHandler case with the DapperAOT source generator, then inspect the generated code and compare its serialization and deserialization behavior. Done means custom TypeHandler implementations are picked up and respected by generated code.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- databases, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100