You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For support questions, please consider using Gitter - Chat
I'm submitting a ...
bug report
feature request
question about the decisions made in the repository
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem
What is the expected behavior?
As a user, I should be able to add extra information when firing a Page tracking event using Segment, so I can gain more granular information on user behavior
What is the motivation / use case for changing the behavior?
* https://segment.com/docs/libraries/analytics.js/#page
*
* analytics.page([category], [name], [properties], [options], [callback]);
*/
pageTrack(path: string) {
// TODO : Support optional parameters where the parameter order and type changes their meaning
try {
analytics.page(path);
} catch (e) {
if (!(e instanceof ReferenceError)) {
throw e;
}
}
}
The jsdoc even shows the ability to add these options parameters, which makes it very confusing (and a tad bit frustrating)
For support questions, please consider using Gitter - Chat
I'm submitting a ...
bug report
feature request
question about the decisions made in the repository
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem
What is the expected behavior?
As a user, I should be able to add extra information when firing a Page tracking event using Segment, so I can gain more granular information on user behavior
Right now, the Page track method only supports a string, which severely inhibits the behavior of Segment's Page method.
The jsdoc even shows the ability to add these options parameters, which makes it very confusing (and a tad bit frustrating)
The text was updated successfully, but these errors were encountered: