What kind of change does this PR introduce?
This PR adds a version number of the openadapt build to posthog events, so its easier to debug the source of erroneous events. It also adds a fix so that submenus in the tray, that have the name of the recording are not reported, rather the underlying action is reported
Summary
Address #768
Checklist
[x] My code follows the style guidelines of OpenAdapt
[x] I have performed a self-review of my code
[ ] If applicable, I have added tests to prove my fix is functional/effective
[x] I have linted my code locally prior to submission
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation (e.g. README.md, requirements.txt)
[x] New and existing unit tests pass locally with my changes
How can your code be run and tested?
In utils.py, comment out the lines that disable posthog in the get_posthog_instance function. I have added a property to psothog events that will differentiate dev events from events coming from the app, so this can be used when we need to test without polluting the events charts. Play around with the tray (also the submenus) and check that the events are logged correctly
What kind of change does this PR introduce? This PR adds a version number of the openadapt build to posthog events, so its easier to debug the source of erroneous events. It also adds a fix so that submenus in the tray, that have the name of the recording are not reported, rather the underlying action is reported
Summary Address #768
Checklist
How can your code be run and tested? In
utils.py
, comment out the lines that disable posthog in theget_posthog_instance
function. I have added a property to psothog events that will differentiate dev events from events coming from the app, so this can be used when we need to test without polluting the events charts. Play around with the tray (also the submenus) and check that the events are logged correctly