Skip to content

feat(low-value-spans): Add low-value span issue UI#115870

Merged
ArthurKnaus merged 2 commits into
masterfrom
arthurknaus/feat/low-value-spans-config-ui
May 20, 2026
Merged

feat(low-value-spans): Add low-value span issue UI#115870
ArthurKnaus merged 2 commits into
masterfrom
arthurknaus/feat/low-value-spans-config-ui

Conversation

@ArthurKnaus
Copy link
Copy Markdown
Member

@ArthurKnaus ArthurKnaus commented May 20, 2026

Add frontend support for low-value span configuration issues once the backend group type is available.

Configuration Issue UI

The new issue type maps to "AI Detected Low-Value Span" and gets a simple details view that follows the existing source-map configuration issue layout.

Feature Gating

The shared Sentry Configuration taxonomy now appears when either the source-map configuration flag or the low-value span configuration flag is enabled, including navigation and Command Palette entries.

Note: ATM no low-value span feature flag is enabled. This is just code scaffolding and not yet visible to anyone.

Depends on #115868
Refs TET-2198

Add frontend type plumbing and a simple configuration issue details view for low-value span findings. Gate the Sentry Configuration taxonomy behind either the source-map or low-value span visibility flag so the shared page can appear during separate rollouts.

Refs TET-2198
Co-Authored-By: Codex <noreply@example.com>
@linear-code
Copy link
Copy Markdown

linear-code Bot commented May 20, 2026

TET-2198

@github-actions github-actions Bot added the Scope: Frontend Automatically applied to PRs that change frontend components label May 20, 2026
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 20, 2026

📊 Type Coverage Diff

✅ No new type safety issues introduced. Coverage: 93.56%

Comment on lines +15 to +23
export function LowValueSpanIssueDetails(_props: LowValueSpanIssueDetailsProps) {
return (
<div>
<ProblemSection />
<SectionDivider orientation="horizontal" />
<TroubleshootingSection />
</div>
);
}
Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

All the content is pure 🤖 output to provide a skeleton. Will heavily rework the sections.

@ArthurKnaus ArthurKnaus requested a review from a team May 20, 2026 07:24
@ArthurKnaus ArthurKnaus changed the title feat(low-value-spans): Add low-value span configuration UI feat(low-value-spans): Add low-value span issue UI May 20, 2026
Keep the Sentry Configuration feature flag list local to the taxonomy module so knip does not report it as an unused export.

Refs TET-2198
Co-Authored-By: Codex <noreply@example.com>
@ArthurKnaus ArthurKnaus marked this pull request as ready for review May 20, 2026 07:30
@ArthurKnaus ArthurKnaus requested review from a team as code owners May 20, 2026 07:30
@ArthurKnaus ArthurKnaus merged commit 9baac3b into master May 20, 2026
71 of 72 checks passed
@ArthurKnaus ArthurKnaus deleted the arthurknaus/feat/low-value-spans-config-ui branch May 20, 2026 09:47
JonasBa pushed a commit that referenced this pull request May 21, 2026
Add frontend support for low-value span configuration issues once the
backend group type is available.

**Configuration Issue UI**

The new issue type maps to "AI Detected Low-Value Span" and gets a
simple details view that follows the existing source-map configuration
issue layout.

**Feature Gating**

The shared Sentry Configuration taxonomy now appears when either the
source-map configuration flag or the low-value span configuration flag
is enabled, including navigation and Command Palette entries.

**Note:** ATM no low-value span feature flag is enabled. This is just
code scaffolding and not yet visible to anyone.

Depends on #115868
Refs TET-2198

---------

Co-authored-by: Codex <noreply@example.com>
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