fix(widget-builder): Prevent crash when threshold max_values is undefined - #124855
Merged
Merged
Conversation
…efined to force checks everywhere
Contributor
Story previewsPreview the stories changed in this PR on the Vercel deployment: Preview deployment: https://sentry-r2t7ormgg.sentry.dev |
TkDodo
approved these changes
Sep 18, 2026
Collaborator
|
bugbot run |
Contributor
There was a problem hiding this comment.
✅ Bugbot reviewed your changes and found no new issues!
Comment @cursor review or bugbot run to trigger another review on this PR
Reviewed by Cursor Bugbot for commit c9d704a. Configure here.
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.
This PR addresses a
TypeError: Cannot read properties of undefined (reading 'max1')occurring in the widget builder's thresholds step.The root cause was identified in
static/app/views/dashboards/widgetBuilder/buildSteps/thresholdsStep/thresholds.tsx. Lines 105-106 attempted to accessthresholdsConfig?.max_values[ThresholdMaxKeys.MAX_1](andMAX_2). WhilethresholdsConfigwas optionally chained,max_valuesitself was not. IfthresholdsConfigexisted butmax_valueswasundefined(which can happen despite the TypeScript type declaring it as required), the bracket accessundefined['max1']would throw a TypeError.The fix involves adding optional chaining (
?.) to themax_valuesproperty access, changingthresholdsConfig?.max_values[key]tothresholdsConfig?.max_values?.[key]. This ensures that ifmax_valuesisundefined, the expression short-circuits, and the?? ''fallback correctly provides an empty string, preventing the crash.A regression test has been added to
thresholds.spec.tsxto cover the scenario wheremax_valuesisundefined, ensuring the component renders correctly without errors.Legal Boilerplate
Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.
Fixes JAVASCRIPT-3BYC
@sentry <feedback>: Autofix iterates on these changes@sentry stop iterating: Autofix stops iterating on this runThis PR was automatically generated by Sentry. You can adjust this setting at any time.