-
Notifications
You must be signed in to change notification settings - Fork 5
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
Returning Errors rather that raising them #51
Comments
Thanks @rscottweekly - do you have a use case where this caused you difficulties? Might you be happy to share some details? |
Thanks for publishing this by the way, its made me code for a few audits so so much easier! I'm a paeds anaesthetist doing work with drug dosing for children living with obesity based on the SOBA guidelines. The root cause of this was a bug on my end that caused it (I had transposed sex and age) in the call to The values called in
which are obviously invalid values - the problem being they just get passed down to So the challenge was I was sending invalid data to Does that make sense? Am happy to do a PR if you'd like to resolve the issues? |
Thank you @rscottweekly that is great. You are right that the error handling could be better. We possibly rely too heavily on the API and server infront of all this. Yes please, very happy to look at a PR - thank you |
I'm not sure if this is deliberate but in uk_who.py, there are a few lines where errors are returned rather than raised - e.g. lines 150 & 167 - which means they don't get caught in the try-block and instead crash the programme further down.
The text was updated successfully, but these errors were encountered: