Lint analytics event exceptions on actual name#9539
Merged
Conversation
changelog: Internal, Automated Testing, Improve developer experience of analytics event name linter
zachmargolis
approved these changes
Nov 3, 2023
zachmargolis
approved these changes
Nov 3, 2023
Merged
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.
🛠 Summary of changes
As a slight alteration to #9480, exempts legacy methods by their actual names, not the expected name.
This was prompted by a proposed change which would have been permitted under the previous logic, but such renames are good opportunities to adopt the new naming convention.
📜 Testing Plan
app/services/analytics_events.rbto rename any string event namerubocop app/services/analytics_events.rb