DapperLib / DapperLib/Dapper

Fix 'ITypeHandler' 'SetValue' method can't intercept 'ValueType' and 'String' type

Open
#1,298 1 comment 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

If the typeHandlers.TryGetValue(type, out handler) method should be ranked higher, the typeMap has a list of base types so that 'ITypeHandler' 'SetValue' will have no effect on rewriting the base types.
image

To change the
image

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 inspecting the typeHandlers.TryGetValue(type, out handler) lookup, the typeMap of base types, and ITypeHandler.SetValue. Reproduce the ValueType and String cases shown in the issue, then verify that a registered handler can intercept them instead of the base-type mapping taking precedence.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
database
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
32/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.