-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
feat(data-management): add custom events list #11463
Conversation
If it helps, I'm also happy to hide the UI changes (two new filter options) and split them to a different PR to get the backend stuff merged quicker. |
… data locally... testing a timeout
posthog/api/event_definition.py
Outdated
@@ -77,6 +77,7 @@ def get_queryset(self): | |||
|
|||
params = { | |||
"team_id": self.team_id, | |||
"starts_with_dollar": "$%", |
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.
nit: the key name sounds pretty specific. Thoughts on calling this is_posthog_event
?
@@ -41,6 +41,18 @@ const eventTypeOptions: LemonSelectOptions<CombinedEventType> = [ | |||
icon: <UnverifiedEvent />, | |||
'data-attr': 'event-type-option-event', | |||
}, | |||
{ |
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.
If its not too much work, it'd be nice to use a divider or indent these sub types since these extra entries could be confusing. Otherwise +1 to hiding this in the UX for this PR and adding in a smaller future one
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.
Looks like a good change. I think the event option labels would be easier to use if we changed the format of a few. I drew a quick update. Have we flagged these changes for documentation? I can see how users might need more explanation on what each type represents.
What about the other event classifications we've used - specifically verified and raw events. Should those be available here? @alexkim205 thoughts on those other event types?
https://www.figma.com/file/rnaKSVMfWTcpX4cmDbvWsi/Data-Management-%26-Live-Events?node-id=4%3A18853
Thanks @alexkim205 and @clarkus ! I'll split the frontend/product work into a separate PR for another round of feedback, and merge in the ✅ 'd backend changes to unblock #11467 |
going to move this to a separate PR
Problem
I'm trying to remove the last references to the "load all data"-powered
eventDefinitionsModel
.We have a dropdown for custom events under insights/paths, which uses this model. I want to convert it to a regular paginated taxonomic filter dropdown.
The shortest amount of changes to get this working is to split the
event_type
used by theevent_definitions
API endpoint to contain two new sub-types:As a side effect, we can now add these two items under data management event list as well:
Changes
event_posthog
andevent_custom
, which take all events and either keep or remove those that start with a dollar$
.How did you test this code?
Wrote tests for the two new filters in the API.