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

Exception handling #30

Open
dg46 opened this issue Jan 25, 2022 · 1 comment
Open

Exception handling #30

dg46 opened this issue Jan 25, 2022 · 1 comment

Comments

@dg46
Copy link
Collaborator

dg46 commented Jan 25, 2022

Currently, we have only minimal handling of exceptions. Given that causal analyses with cause2e have a mostly fixed structure, it would be helpful for the users to receive clearer feedback, at least whenever their input for the main analysis methods cannot be processed as desired.

Steps:

  • identify frequent sources of errors
  • write custom exception types for them to avoid confusion with other errors
  • handle each exception in a way that enables the users to adapt their input accordingly (or inform them whenever the desired functionality is implemented)
@dg46
Copy link
Collaborator Author

dg46 commented Jan 25, 2022

An example for the desired state of exception handling is the recently added spellchecking for variable names in the domain knowledge, which is handled by telling the user the name of the problematic variable and asking them to do a spellcheck on their input.

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

No branches or pull requests

1 participant