Refactor alert message builder to improve type handling and error man… #1812
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…agement - Updated `AlertType` to use `BaseAlertsGroup` as a more generic base type - Added explicit type checking and error handling for unknown alert types - Modified `_get_alert_subtitle_blocks()` and `_get_alert_groups_blocks()` to raise `ValueError` for unrecognized alert types - Simplified type handling in alert message generation
Contributor
|
👋 @MikaKerman |
ofek1weiss
approved these changes
Feb 12, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…agement
AlertTypeto useBaseAlertsGroupas a more generic base type_get_alert_subtitle_blocks()and_get_alert_groups_blocks()to raiseValueErrorfor unrecognized alert types