Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Better error messages for .*Async methods when not using DbConnection #986

Merged
merged 3 commits into from
Apr 4, 2018

Conversation

NickCraver
Copy link
Member

Perhaps in v2 we move these to DbConnection itself ratherr than IDbConnection for the extensions to eliminate the case, but that's breaking...for now we can at least throw a better error. See #757 for details.

@mgravell note: I'm now passing a cancellation token (effectively unused...but fixes when we normalize them all in v2) in MultiMapAsync (line 963 below). I assume this was just an oversight initially but if there's a reason let me know and I can back that out & add a comment on why.

Perhaps in v2 we move these to DbConnection itself ratherr than IDbConnection for the extensions to eliminate the case, but that's breaking...for now we can at least throw a better error. See #757 for details.
@NickCraver NickCraver merged commit e199a87 into master Apr 4, 2018
@NickCraver NickCraver deleted the craver/async-errors branch September 10, 2018 15:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants