-
-
Notifications
You must be signed in to change notification settings - Fork 4.5k
chore(sub v3): prep for EA #101437
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
chore(sub v3): prep for EA #101437
Conversation
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
Comment on lines
+37
to
+43
| for (let i = routes.length - 1; i >= 0; i--) { | ||
| const route = routes[i] as RouteWithName; | ||
| if (route?.name) { | ||
| feedbackSource = route.name; | ||
| break; | ||
| } | ||
| } |
Member
Author
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the route name we desire for feedbackSource is always the last route in routes with a name
dashed
approved these changes
Oct 14, 2025
| subscription, | ||
| addOnCategory: row.addOnCategory, | ||
| isOpen: !!isOpen, | ||
| }); |
Contributor
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
chromy
pushed a commit
that referenced
this pull request
Oct 17, 2025
- Start replay recording every time any of the Usage & Billing settings pages are navigated to - Remove `trackSubscriptionView`; this event has been removed and we can use the automated Page View events instead - Add route analytics param for whether the page view is with the new UI flag - Automatically add analytics params for new checkout and new UI for all events defined in `trackGetsentryAnalytics`, instead of needing to manually add these flags for every relevant event - Adds some missing analytics events - Add feedback form button to every Usage & Billing settings page Closes BIL-1594, BIL-1595, and BIL-1640
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
trackSubscriptionView; this event has been removed and we can use the automated Page View events insteadtrackGetsentryAnalytics, instead of needing to manually add these flags for every relevant eventCloses BIL-1594, BIL-1595, and BIL-1640