-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Dashboard csv export v2 continued #6455
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
+558
−201
Merged
Changes from 4 commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
bb2c3cf
add event:prop_key (internal API only, breakdown only) dimension
RobertJoonas ae12933
add custom_props.csv
RobertJoonas 0d47e82
add conversions.csv
RobertJoonas 17d5a74
fix csv e2e test flakiness
RobertJoonas be7997c
limit prop_key query
RobertJoonas 8f251f1
split function into smaller functions
RobertJoonas 1632261
explicit isRevenueAvailable: false
RobertJoonas a480a5d
Merge branch 'master' into dashboard-csv-export-v2-continued
RobertJoonas File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
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.
suggestion, non-blocking: The function
getCustomPropsMetricsdepends onisRevenueAvailable, which isn't passed.It seems we actually want to say that in the CSV report, revenue is not available (
isRevenueAvailable: false), or do we? With MetricContext allowing undefined, I can't actually tell what the intent is for this CSV report.I think we shouldn't allow undefined in MetricContext.
Shorter args list at call sites is not worth losing explicitly declared intent at call sites.
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.
Yeah, the intent is that revenue is not available. No specific reason other than sticking to legacy behaviour.
IMHO it doesn't (currently) hurt readability because the behaviour between
undefinedandfalseis equivalent. Everything in theMetricContextthat is irrelevant from the caller's perspective can simply be left unspecified and get interpreted as false, which, at least to me, is quite intuitive.This would change with the addition of a context variable that would have a default value of true, but that's not the case, and I doubt it ever will be?
That said though, I've written out
isRevenueAvailable: falseto make this specific case explicit. 1632261.