-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
chore(insights): rename the value field in multiple breakdowns #23890
Conversation
📸 UI snapshots have been updated11 snapshot changes in total. 0 added, 11 modified, 0 deleted:
Triggered by this commit. |
Size Change: 0 B Total Size: 1.07 MB ℹ️ View Unchanged
|
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.
Snapshots are correct. They reverted to prior multiple breakdowns changes in Funnels: 7a3e849#diff-97ccf0cbc4b249f761838d67a3d9ccc7af51e8d5fbd01f6a871afcb22208c1a7.
…ostHog/posthog into chore/rename-field-multiple-breakdowns
@thmsobrmlr a few notes about the PR:
|
For posterity, this gives us all insights from our team already using the trends multi-breakdowns: SELECT filters->>'breakdowns', team_id, * FROM posthog_dashboarditem
WHERE filters->>'breakdowns' IS NOT NULL
AND filters->'breakdowns'->0->>'property' IS NULL |
Co-authored-by: Thomas Obermüller <[email protected]>
📸 UI snapshots have been updated2 snapshot changes in total. 0 added, 2 modified, 0 deleted:
Triggered by this commit. |
📸 UI snapshots have been updated1 snapshot changes in total. 0 added, 1 modified, 0 deleted:
Triggered by this commit. |
📸 UI snapshots have been updated2 snapshot changes in total. 0 added, 2 modified, 0 deleted:
Triggered by this commit. |
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.
LGTM if looks good to Thomas, just is it expected for this dashboard to be blank?
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.
There is a fix for that: #23904. I merged the master branch, so let me check if it fixes the snapshot.
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.
Indeed, it has fixed the snapshot.
…-field-multiple-breakdowns
…ostHog/posthog into chore/rename-field-multiple-breakdowns
…ostHog/posthog into chore/rename-field-multiple-breakdowns
📸 UI snapshots have been updated2 snapshot changes in total. 0 added, 2 modified, 0 deleted:
Triggered by this commit. |
📸 UI snapshots have been updated1 snapshot changes in total. 0 added, 1 modified, 0 deleted:
Triggered by this commit. |
📸 UI snapshots have been updated2 snapshot changes in total. 0 added, 2 modified, 0 deleted:
Triggered by this commit. |
📸 UI snapshots have been updated3 snapshot changes in total. 0 added, 3 modified, 0 deleted:
Triggered by this commit. |
📸 UI snapshots have been updated1 snapshot changes in total. 0 added, 1 modified, 0 deleted:
Triggered by this commit. |
…og#23890) Co-authored-by: github-actions <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Thomas Obermüller <[email protected]>
Problem
The PR renames the
value
toproperty
field to improve backward compatibility with legacy multiple breakdowns because there are 17k+ saved funnels with the old shape.Changes
Does this work well for both Cloud and self-hosted?
Yes
How did you test this code?
Existing unit tests and manual testing.