Repository navigation
Fix response type parsing - #307
Merged
Merged
Conversation
nucleus-ffm
force-pushed
the
fix/response_type
branch
from
August 21, 2026 16:32
7d79e9c to
98f3e77
Compare
nucleus-ffm
force-pushed
the
fix/response_type
branch
from
August 21, 2026 16:38
98f3e77 to
173631c
Compare
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
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.
The parsing of the response type broke when alerts used multiple response types. This fixes the parsing and also adds a tag in the alert detail view to display the response type.