DapperLib / DapperLib/Dapper

Delegate from one custom type handler to another.

Open
#1,926 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C#
Stars
18.4k
Forks
3.7k
Avg merge
5h 8m
Merged PRs (30d)
1

Description

Let's say I have a value object (to avoid primitive obsession) and I want to create a custom type handler that internally just delegates to the appropriate type handler for the type backing my value object (e.g., treat record Username(string Value) as string, and make its type handler simply take Value and handle that instead using whichever type handler exists for a string type).

I considered the possibility of using SqlMapper.LookupDbType, but that's deprecated, and documentation says it's for internal use only. Are there any safe workarounds for this?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the custom type-handler behavior described in the issue and the referenced SqlMapper.LookupDbType API and its documentation. Determine whether a supported delegation mechanism can be specified; done would be a documented safe workaround or a clearly scoped API change for handlers backing value objects.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
database
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.