Remove isLegacyAlert from the anomaly thresholds hook - #121464
Merged
Conversation
github-actions
Bot
added
the
Scope: Frontend
ceorourke
force-pushed
the
ceorourke/rm-islegacyalert-frontend
branch
from
August 6, 2026 20:11
debec00 to
4009ad3
Compare
ceorourke
marked this pull request as ready for review
August 6, 2026 20:16
saponifi3d
approved these changes
Aug 6, 2026
ceorourke
force-pushed
the
ceorourke/rm-islegacyalert-frontend
branch
from
August 7, 2026 17:21
4009ad3 to
4f14af0
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
2 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.
Now that the backend never expects this, we can remove the front end usage of legacy alerts for anomaly detection.