-
Notifications
You must be signed in to change notification settings - Fork 142
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
Automatic click user action collection #338
Conversation
d2a6760
to
f6174ed
Compare
f6174ed
to
8c3771b
Compare
This commit addresses typings issues in the E2E tests to make tests more easier to write. RUM events returned by the server are not the same as those used accross the sdk. Typically, their properties are snake cased instead of camelCased. To improve this, we remove the SDK types usages, and replace them by custom types used only for those tests. A bit of typings are repeated, but it makes the DX more easier. Those types can be adjusted at will for the tests needs. Some grobal types have been adjusted too.
8c3771b
to
1a4fe75
Compare
And associated variable names
1a4fe75
to
2312a55
Compare
Codecov Report
@@ Coverage Diff @@
## master #338 +/- ##
=======================================
Coverage 86.92% 86.92%
=======================================
Files 29 29
Lines 1621 1621
Branches 333 333
=======================================
Hits 1409 1409
Misses 212 212 Continue to review full report at Codecov.
|
Having two separate variables makes things more explicit
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 also removes the LongTask startTime property that was added inadvertently by #338
* 🐛 [RUM] user action duration should be in ns * [RUM] change userActionId to userAction.id * 🏷 [RUM] adjust types This also removes the LongTask startTime property that was added inadvertently by #338
This PR implements the automatic click user action collection based on the previous POC.
For now, it is behind the
collect-user-actions
feature flag.Future steps will include:
user_action.measures
)