Chris Chilvers

Dapper doesn't support custom type handlers for in-built primitive types at the moment, see #303 #206 and #458

Not at the moment, the main reason is it could be a breaking change for existing code as the simple solution is to move the check for `ITypeHandler` earlier in...

I don't thing you need to touch the IL sections. It's mostly a case of changing the order of the type checks to look for a custom handler first. At...

@kbilsted my main concern would be the external 3rd-party code that could get an unexpected change in behaviour, i.e. a type handler that was previously doing nothing and had been...

Could hide it behind a feature flag, or add a new interface such as `SqlEnumConverter` so that unless you explicitly use the new features it won't affect existing code. Only...

Ideally I think auto-mapping should ignore properties in sub-classes that are already mapped by a super-class rather than mapping the same property twice. ### Cases 1. super-class is not mapped,...

Yeah, I couldn't see any way to avoid that. Could add a flag to enable the new behaviour but not sure how you'd feel about that.

@peterthomastlc the problem is it changes behaviour for existing apps. If an existing app had a custom type handler for and enum before this change the handler wouldn't have been...

I have a similar issue, date are treated as categories rather than continuous numbers (since they're seen as a string/object). The issue with treating a date as a category means...

I've created a quick mock of something that works in d3, so the question is how would you render this same data in recharts? https://codesandbox.io/s/example-date-range-using-d3-7f7qz Note how even with the...