-
Notifications
You must be signed in to change notification settings - Fork 16
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
Passing a datetime tuple parameter in place of some other type results in badarg instead of {pgo_protocol, {parameters, Expected, Got}} #83
Comments
Ah yup, thanks. Think I can fix. |
Thank you |
Hm, I just tried to reproduce and it seemed to work as expected:
I was adding it as a test to
|
With
|
Just noticed they used a timestamp and I was using a datetime. But I just checked and the same thing happens:
|
Oh strange... I'll try and reproduce it later. Thanks |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello!
We've discovered a surprising behaviour where for date times specifically if they are given when a different argument type is not supplied then the usual descriptive
{pgo_protocol, {parameters, Expected, Got}}
error it gives justbadarg
.Given this is different to the behaviour of other parameter type errors I think this is a bug.
Thanks,
Louis
Related: lpil/pgo#29
The text was updated successfully, but these errors were encountered: