Rick Drizin

Well, I think you're right that the provided code was not a good example. Since I didn't use `using` the `Dispose()` is not invoked and therefore the connection remains there...

I feel that we should be supporting custom TypeHandlers. Reopening in case someone volunteers to add support for that.

@ryburn52 C# compiler doesn't provide the names of interpolated variables, so you'd have to provide them as `format` or wrap under an `anonymous object` or some other type. As reference...

Not sure if I understood what you want, but have you checked the [`:raw`](https://github.com/Drizin/DapperQueryBuilder/#raw-strings) modifier? You should be able to do something like: `query.AppendLine($"Select * from {nameof(Users):raw} Where {nameof(Users.ModifiedDate):raw}>= {asOfDate:@asOfDate}");`...

DapperQueryBuilder is being deprecated and this repo will be archived soon. The replacement library is [InterpolatedSql.Dapper](https://github.com/Drizin/InterpolatedSql/tree/main/src/InterpolatedSql.Dapper). I'll move this issue to that new repo.

InterpolatedSql.Dapper provides better extensibility support. Here is a quick example of how you can customize the parameter names: ```cs using InterpolatedSql.Dapper; // ... public class MyCustomSqlParameterMapper : SqlParameterMapper { public...

Haven't tested, but on a very quick look I think `InterpolatedSqlParser.TransformArgument` sends the `argumentFormat` as `ref string`, then whatever types/hints can be extracted from that are extracted and removed from...

I didn't get it. Can you please provide a sample code to reproduce the problem?

Looks like this bug happens when Dapper expands an empty array. Please test with latest package 2.4.0

Relevant commit https://github.com/Drizin/InterpolatedSql/commit/a2333126910a4b537cd0e9849528d656e80967ac