Remove fallback logging for unknown frontend event#10086
Merged
Conversation
changelog: Internal, Analytics, Remove fallback logging for unknown frontend event
mitchellhenke
approved these changes
Feb 14, 2024
Contributor
mitchellhenke
left a comment
mitchellhenke
left a comment
There was a problem hiding this comment.
Thanks for the cleanup!
zachmargolis
approved these changes
Feb 14, 2024
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.
🛠 Summary of changes
Removes fallback logging for frontend events which aren't recognized.
This was added as a temporary measure in #9438 to ensure that we hadn't missed any frontend events.
There are no logs associated with this event, indicating that all of our event names are captured.
📜 Testing Plan
Bonus: Initiate a request to
POST /api/loggerwith an unrecognized event name and verify you get a 400 response.