-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Start point for paths #897
Conversation
return event, path_type, event_filter, start_comparator | ||
|
||
@action(methods=['GET'], detail=False) | ||
def elements(self, request: request.Request): |
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.
added an endpoint off the /paths that will retrieve the top 50 elements that a user can use as a start point. could possibly belong somewhere else but we don't have a dedicated elements endpoint and this is a specific need here
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.
This has made paths very useful!
- The hover says
undefined -> undefined
- In my case, there's 2 posthog.com starting points. Looking at what the api returns, this might be an issue in the frontend.
Trying to debug that 2nd issue further, this is what happens when I specify app.posthog.com/trends:
Api seems to be correct but there's still irrelevant pages in position 1
- These dropdowns don't seem 100% aligned
@timgl Ready for another look! |
Changes
Todo:
Checklist