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

feat: Implement Exception Chaining for Better Error Traceability #18

Open
Karanjot786 opened this issue Aug 7, 2024 · 0 comments
Open
Assignees

Comments

@Karanjot786
Copy link
Member

Description:

To enhance error traceability throughout the codebase, we need to implement exception chaining. Currently, the exception handling does not provide sufficient context for the underlying errors. By using exception chaining, we can improve the clarity and traceability of errors.

Tasks:

  1. Identify all instances of exception handling across the codebase.
  2. Replace the current exception handling with exception chaining.
    • Example:
      except Exception as exc:
          raise Exception("My own text") from exc
  3. Ensure all exception messages provide clear and meaningful context.
  4. Update any related test cases to verify the new exception chaining behavior.

References:

Refer to Python's documentation on exception chaining for more details.

Files to Update:

  • crategen/converters/tes_converter.py
  • crategen/converters/wes_converter.py
  • crategen/converter_manager.py
  • crategen/validators.py
  • Any other file where exceptions are handled.

Expected Outcome:

  • Improved error traceability and clarity throughout the codebase.
  • Consistent and meaningful exception messages that provide context for the underlying errors.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

No branches or pull requests

2 participants