feat: Handle new DRAWBRIDGE_ISSUE alert cause#2988
Merged
robbie-sundstrom merged 1 commit intomainfrom Apr 3, 2026
Merged
Conversation
rwaskiewicz
approved these changes
Apr 2, 2026
Contributor
rwaskiewicz
left a comment
rwaskiewicz
left a comment
There was a problem hiding this comment.
From my (newbie) point of view, this seems to align with how other variants of the cause type have been defined in the past. Looks good to me, but I probably shouldn't be considered that reliable just yet 😅
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
3 participants
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.
Asana task: Screens: support new alert cause DRAWBRIDGE_ISSUE
Handle the new potential
Alert.causetype,DRAWBRIDGE_ISSUE. Also adds a grammar rule for it so that it's described as "due to a drawbridge issue".Confirmed that there's nowhere else in the code that we need to handle this new type of cause.