Skip to content
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

feat(replays): add initial replay cards to replay list #53323

Merged
merged 10 commits into from
Jul 21, 2023

Conversation

michellewzhang
Copy link
Member

@michellewzhang michellewzhang commented Jul 21, 2023

closes #53086

created two experimental tables on the replay list page:

  1. top 3 most erroneous replays within the last 7 days
  2. top 3 most dead click replays within the last 7 days
    (can change these time periods, I just thought 1 day was too little time for a useful sample size since a lot of numbers showed 0)

notes:

  • these tables are static when compared to the big replay list table, so pagination doesn't affect them (see below for screenshots showing this)
  • in theory, rage clicks always < dead clicks, which is why I chose to sort by dead clicks

page 1:
SCR-20230721-jybf

page 2 (same tables, different replays on big list):
SCR-20230721-jxge

@github-actions github-actions bot added the Scope: Frontend Automatically applied to PRs that change frontend components label Jul 21, 2023
Comment on lines +138 to +142
const SplitCardContainer = styled('div')`
display: grid;
grid-template-columns: 1fr 1fr;
gap: ${space(2)};
`;
Copy link
Member

Choose a reason for hiding this comment

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

Grid! looks so easy once it's working!

static/app/views/replays/replayTable/index.tsx Outdated Show resolved Hide resolved
static/app/views/replays/replayTable/index.tsx Outdated Show resolved Hide resolved
fetchError={fetchError}
isFetching={isFetching}
replays={replays?.slice(0, 3)}
sort={eventView.sorts[0]}
Copy link
Member

Choose a reason for hiding this comment

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

what if this was sort={undefined}

Copy link
Member Author

Choose a reason for hiding this comment

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

YES

@michellewzhang michellewzhang requested review from a team and removed request for a team July 21, 2023 18:38
@michellewzhang michellewzhang merged commit 82a85ca into master Jul 21, 2023
@michellewzhang michellewzhang deleted the mz/add-replay-cards branch July 21, 2023 19:20
armenzg pushed a commit that referenced this pull request Jul 24, 2023
closes #53086

created two experimental tables on the replay list page: 
1. top 3 most erroneous replays within the last 7 days
2. top 3 most dead click replays within the last 7 days
(can change these time periods, I just thought 1 day was too little time
for a useful sample size since a lot of numbers showed 0)

notes:
- these tables are static when compared to the big replay list table, so
pagination doesn't affect them (see below for screenshots showing this)
- in theory, rage clicks always < dead clicks, which is why I chose to
sort by dead clicks

page 1:
<img width="1250" alt="SCR-20230721-jybf"
src="https://github.com/getsentry/sentry/assets/56095982/1c2f6981-e504-4d90-9f88-4c4dfc4523f5">


page 2 (same tables, different replays on big list):
<img width="1238" alt="SCR-20230721-jxge"
src="https://github.com/getsentry/sentry/assets/56095982/d4b231e3-8786-4144-8122-cc57af0ef3ca">
@github-actions github-actions bot locked and limited conversation to collaborators Aug 6, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Scope: Frontend Automatically applied to PRs that change frontend components
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Experiment with Error & Rage/Dead click Cards at the top of the Replay List page
2 participants