You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please fix this ASAP, DeleteAsync doesn't work with any predicates and i will explain why
Right now your code is like this
both methods always call to
never go to
The Fix is very easy, just ad this
in this way the "runtime" must know which method use it
Why the issue is happening? simple
Both definitions have conflicts because one use generic T in the second parmeter and the other use object in the second parameter, if you doesn't expecify the generic T, "runtime" assume the generic method and never go to the object method, so if you especify the generic T, now "runtime" must know wich value is T.
please add the generic T in this method like this
I doens't know why nobody show this critical bug, DeleteAsync with predicates is usless
The text was updated successfully, but these errors were encountered:
I'm having this exact same problem. I'm using a custom default mapper so calling DeleteAsync() without the generic parameter is causing Dapper to try and load CustomAutoClassMapper<Object>. Understandably, this doesn't work so well.
Please fix this ASAP, DeleteAsync doesn't work with any predicates and i will explain why
Right now your code is like this
both methods always call to
never go to
The Fix is very easy, just ad this
in this way the "runtime" must know which method use it
Why the issue is happening? simple
Both definitions have conflicts because one use generic T in the second parmeter and the other use object in the second parameter, if you doesn't expecify the generic T, "runtime" assume the generic method and never go to the object method, so if you especify the generic T, now "runtime" must know wich value is T.
please add the generic T in this method like this
I doens't know why nobody show this critical bug, DeleteAsync with predicates is usless
The text was updated successfully, but these errors were encountered: