Skip to content

Conversation

@Fondryext
Copy link
Contributor

This PR upgrades our analytics calls to the next major version, also called the Events API. As part of this work, analytics calls have changed shape, and some deprecated properties have been dropped.
J=WAT-4651
TEST=auto,manual

Updated auto tests. Ran test site locally and saw events all the way to snowflake.

@github-actions
Copy link
Contributor

github-actions bot commented Apr 7, 2025

Current unit coverage is 90.83735203857957%
Current visual coverage is 78.1094527363184%
Current combined coverage is 91.45111793073214%

@coveralls
Copy link

coveralls commented Apr 7, 2025

Coverage Status

coverage: 87.704% (-0.6%) from 88.287%
when pulling d9b1f21 on dev/events-api
into f4c07d7 on main.

@Fondryext Fondryext marked this pull request as ready for review June 24, 2025 13:45
@Fondryext Fondryext requested a review from a team as a code owner June 24, 2025 13:45
searchTerm?: string;
}

//todo - how many of these do we want to delete?
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I want to prune these down - open to what we use as our canonical list.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there a reason we want to prune these down? At the very least, I imagine we want things like map pin, auto complete selection, the paginates, chat impression, search clear, etc.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So as we discussed, let's pare this down based on user event types and then consider any remaining enum types more individually. If it's clearly search related or has been used before, include it. If it's clearly for another product, exclude it, etc. Use your discretion, but feel free to loop in Baigel / others if you want a 2nd opinion while I'm out.

searchTerm?: string;
}

//todo - how many of these do we want to delete?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there a reason we want to prune these down? At the very least, I imagine we want things like map pin, auto complete selection, the paginates, chat impression, search clear, etc.

Copy link

@vijay267 vijay267 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Generally looks good! Had some comments about specific details, but I like the wrapper, and overall the changes make sense.

searchTerm?: string;
}

//todo - how many of these do we want to delete?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So as we discussed, let's pare this down based on user event types and then consider any remaining enum types more individually. If it's clearly search related or has been used before, include it. If it's clearly for another product, exclude it, etc. Use your discretion, but feel free to loop in Baigel / others if you want a 2nd opinion while I'm out.

Fondryext and others added 9 commits September 22, 2025 14:27
This PR upgrades our analytics calls to the next major
version, also called the Events API. As part of this
work, analytics calls have changed shape, and some deprecated
properties have been dropped.
J=WAT-4651
TEST=auto,manual

Updated auto tests. Ran test site locally and saw events all the
way to snowflake.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants