#1066: When month over month change value doesn't exist, don't add or try to style it #1068
Merged
tunetheweb merged 1 commit intomainfrom Jun 9, 2025
Merged
#1066: When month over month change value doesn't exist, don't add or try to style it #1068tunetheweb merged 1 commit intomainfrom
tunetheweb merged 1 commit intomainfrom
Conversation
tunetheweb
approved these changes
Jun 9, 2025
This was referenced Jun 9, 2025
tunetheweb
added a commit
that referenced
this pull request
Jun 9, 2025
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.
See issue: #1066
For some smaller geos, the month over month change returns null. If that's the case, the MoM stat isn't show in the summary cards. As an extra protection, we're also first checking if the styling object exists before trying to call on its color/direction value (
styling?.colorinstead ofstyling.color).