[FIX] error checking causing panic #103
Merged
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.
This pull request includes changes to the
alert_controller.go
file, specifically within theflattenNotificationGroups
andflattenNotifications
functions. The changes are primarily focused on error handling and flow control.Here are the most important changes:
controllers/alphacontrollers/alert_controller.go
:flattenNotificationGroups
function, the condition for the error check has been modified. Previously, it was checking a variableerr
which wasn't updated inside the loop. Now, it correctly checksflattenErr
, which is the error returned from theflattenNotificationGroup
function. This ensures that any errors encountered during the flattening process are properly caught and handled.flattenNotifications
function, acontinue
statement has been added in the error handling block. This means that if an error occurs when flattening a notification, the function will skip the current iteration and move to the next notification, preventing the erroneous notification from being added to the result.Error sample