Skip to content

commit: feat(processor-pipeline): add domain-specific exception handling #9

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

Merged
merged 1 commit into from
Oct 25, 2024

Conversation

walmir-silva
Copy link
Contributor

BREAKING CHANGE: Add ProcessorRuntimeException for domain-specific error handling

  • Add ProcessorRuntimeException extending RuntimeException
  • Define specific error codes (2601-2605) for processor operations
  • Implement semantic static factory methods for different error scenarios
  • Update ProcessorRegistry to use new exception types

Changes:

  • Add new exception class with domain-specific error handling
  • Update ProcessorRegistry to use new exceptions
  • Improve error messages and error code organization
  • Add consistent PROCESSOR prefix for error codes

This change improves error handling by:

  • Making errors more specific to the processor domain
  • Providing better error tracking and debugging
  • Ensuring consistent error messages
  • Following the established exception hierarchy

BREAKING CHANGE: Add ProcessorRuntimeException for domain-specific error handling

- Add ProcessorRuntimeException extending RuntimeException
- Define specific error codes (2601-2605) for processor operations
- Implement semantic static factory methods for different error scenarios
- Update ProcessorRegistry to use new exception types

Changes:
- Add new exception class with domain-specific error handling
- Update ProcessorRegistry to use new exceptions
- Improve error messages and error code organization
- Add consistent PROCESSOR prefix for error codes

This change improves error handling by:
- Making errors more specific to the processor domain
- Providing better error tracking and debugging
- Ensuring consistent error messages
- Following the established exception hierarchy
@walmir-silva walmir-silva merged commit cb916d9 into main Oct 25, 2024
1 check passed
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

Successfully merging this pull request may close these issues.

1 participant