Consistent error handling #101
Labels
documentation
Improvements or additions to documentation
enhancement
New feature or request
open to PRs
I agree this should be done but don't have the time to do it myself.
Milestone
Error handling right now is a mess, each SSO provider class lets exceptions propagate on their own terms. There should be a straightforward and concise set of exceptions raised from the
verify_and_process
coroutine so that devs can catch the errors and provide end users with relevant information.Once the structure of exceptions is clear, it should be well documented so that contributors know which exceptions to raise when and devs know which exceptions to expect.
The text was updated successfully, but these errors were encountered: