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.
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
[APM] Fix query to mobile transactions main statistics #155895
[APM] Fix query to mobile transactions main statistics #155895
Changes from all commits
5751fb7
6e4955b
c2a41e1
c01244e
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Nesting functions can be useful for encapsulating functionality and scoping variables but in this case, it seems it doesn't provide any value.
On the other hand, if there is a possibility of reusing
ex getMobileErrorEventStatistics
in other parts of the codebase, defining it outside ofgetMobileMainStatisticsByField
could be a more practical approach.What do you think about defining them outside of
getMobileMainStatisticsByField
?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.
I thought about it, but
getMobileErrorEventStatistics
is getting crash errors by field, it's not generic enough to be reusable. But I will keep it in mind for when we start implementing more use cases forcrashRate
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.
tbh, I'm not sure what you meant with it 🤔 but I think something like the following will work