fix(custom): separate result conditions with newlines - #1762
Open
fly1d wants to merge 1 commit into
Open
Conversation
Keep the custom webhook body valid JSON by inserting escaped newline sequences between formatted condition results. Implemented by OpenAI Codex (GPT-5) acting as a coding agent.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
[RESULT_CONDITIONS]entry on a separate line for custom alerts\nseparators so JSON webhook bodies remain validFixes #1485
Testing
go test ./alerting/provider/customgo test ./... -raceThis contribution was implemented and prepared by OpenAI Codex (GPT-5) acting as a coding agent.