Skip to content

feat(dashboards): filter frontend overview by frontend data#107779

Merged
DominikB2014 merged 6 commits intomasterfrom
dominikbuszowiecki/browse-292-filter-by-frontend-project-in-frontend-overview-page
Feb 6, 2026
Merged

feat(dashboards): filter frontend overview by frontend data#107779
DominikB2014 merged 6 commits intomasterfrom
dominikbuszowiecki/browse-292-filter-by-frontend-project-in-frontend-overview-page

Conversation

@DominikB2014
Copy link
Contributor

@DominikB2014 DominikB2014 commented Feb 6, 2026

Following the pattern from the insights page, this PR makes the frontend overview table explicitly filter for frontend data by applying an sdk.name = [...frontendSdks] filter.

This is a little different because the insights filtered for selected frontend projects, and applied a projects = [selectedFrontendProjects] filter, this kept the overall filter string much smaller, but because we're migrating this to dashboards, this is the equivalent way to get it working in dashboards without adding logic into it.

Also threw in a minor change to apply TableWidths = -1 so that the table does not horizontally scroll

@DominikB2014 DominikB2014 requested a review from a team as a code owner February 6, 2026 17:27
@linear
Copy link

linear bot commented Feb 6, 2026

@github-actions github-actions bot added the Scope: Frontend Automatically applied to PRs that change frontend components label Feb 6, 2026
Copy link
Contributor

@cursor cursor bot left a comment

Choose a reason for hiding this comment

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

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.

'sentry.javascript.browser',
'sentry.javascript.electron',
'sentry.javascript.ember',
'sentry.javascript.enrio',
Copy link
Contributor

Choose a reason for hiding this comment

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

Invalid SDK name "sentry.javascript.enrio" is a typo

Medium Severity

The SDK name 'sentry.javascript.enrio' is not a valid Sentry JavaScript SDK. This value doesn't exist anywhere else in the codebase and isn't a recognized SDK. The list already includes 'sentry.javascript.ember' on the line above, so this appears to be either a typo or an erroneous entry. Including this invalid SDK name in the filter won't match any actual data.

Fix in Cursor Fix in Web

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Should be valid, we have an internal spreadsheet which lists them all

@DominikB2014 DominikB2014 merged commit 638996c into master Feb 6, 2026
59 checks passed
@DominikB2014 DominikB2014 deleted the dominikbuszowiecki/browse-292-filter-by-frontend-project-in-frontend-overview-page branch February 6, 2026 18:27
jaydgoss pushed a commit that referenced this pull request Feb 12, 2026
Following the pattern from the insights page, this PR makes the frontend
overview table explicitly filter for frontend data by applying an
`sdk.name = [...frontendSdks]` filter.

This is a little different because the insights filtered for selected
frontend projects, and applied a `projects = [selectedFrontendProjects]`
filter, this kept the overall filter string much smaller, but because
we're migrating this to dashboards, this is the equivalent way to get it
working in dashboards without adding logic into it.

Also threw in a minor change to apply `TableWidths = -1` so that the
table does not horizontally scroll
dcramer pushed a commit that referenced this pull request Feb 17, 2026
Following the pattern from the insights page, this PR makes the frontend
overview table explicitly filter for frontend data by applying an
`sdk.name = [...frontendSdks]` filter.

This is a little different because the insights filtered for selected
frontend projects, and applied a `projects = [selectedFrontendProjects]`
filter, this kept the overall filter string much smaller, but because
we're migrating this to dashboards, this is the equivalent way to get it
working in dashboards without adding logic into it.

Also threw in a minor change to apply `TableWidths = -1` so that the
table does not horizontally scroll
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Frontend Automatically applied to PRs that change frontend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants