Skip to content

Consistent error handlingΒ #101

@tomasvotava

Description

@tomasvotava

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentationenhancementNew feature or requestopen to PRsI agree this should be done but don't have the time to do it myself.

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions