Skip to content

fix(spans-migration): Lock down discover transactions tab completely #95880

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

Merged
merged 4 commits into from
Jul 22, 2025

Conversation

nikkikapadia
Copy link
Member

@nikkikapadia nikkikapadia commented Jul 18, 2025

As part of the spans migration, we're locking down the transactions dataset in discover completely. This will not allow users to select the transactions dataset and save changes to existing transaction queries. I had to make changes to the TabList.Item component to allow passing in tooltip props so i can display the deprecation message.

Closes ENG-4633

@github-actions github-actions bot added the Scope: Frontend Automatically applied to PRs that change frontend components label Jul 18, 2025
Copy link

linear bot commented Jul 18, 2025

@nikkikapadia nikkikapadia marked this pull request as ready for review July 18, 2025 17:44
@nikkikapadia nikkikapadia requested review from a team as code owners July 18, 2025 17:44
cursor[bot]

This comment was marked as outdated.

Comment on lines 429 to 433
tct(
'Discover\u2192Transactions is going to be merged into Explore\u2192Traces soon. Please save any transaction related queries from [traces:Explore\u2192Traces]',
{
traces: <Link to={tracesUrl} />,
}
Copy link
Member

Choose a reason for hiding this comment

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

I see this is used a few places, should we put it into some helper function where we can provide the trace URL?

Comment on lines +129 to +130
disabled: deprecatingTransactionsDataset,
tooltip: deprecatingTransactionsDataset
Copy link
Member

Choose a reason for hiding this comment

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

It seems like when disabled: true, the tooltip hovering doesn't work. You may want to see if there's some kind of styling blocking cursor events 🤔

Copy link
Member

Choose a reason for hiding this comment

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

I think this line is responsible. Maybe we can check if there's tooltip information in the styled component before blocking all pointer events, or maybe there's another setting that we can use.

cursor[bot]

This comment was marked as outdated.

Copy link

@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.

Bug: Tooltips Fail on Disabled Tabs

Tooltips do not display for disabled tabs. Although the Tooltip component wraps the BaseTab, the BaseTab (via its internal TabWrap component) applies pointer-events: none CSS styling when disabled. This styling prevents mouse hover events from reaching the Tooltip wrapper, making it non-functional and defeating the purpose of providing explanatory tooltips for disabled tabs.

static/app/components/core/tabs/tab.tsx#L172-L193

if (tooltipProps) {
return (
<Tooltip {...tooltipProps}>
<BaseTab
tabProps={tabProps}
isSelected={isSelected}
to={to}
hidden={hidden}
disabled={disabled}
orientation={orientation}
overflowing={overflowing}
ref={objectRef}
variant={variant}
as={as}
size={size}
>
{rendered}
</BaseTab>
</Tooltip>
);
}

Fix in CursorFix in Web


Was this report helpful? Give feedback by reacting with 👍 or 👎

@nikkikapadia nikkikapadia merged commit 10c9909 into master Jul 22, 2025
47 checks passed
@nikkikapadia nikkikapadia deleted the nikki/fix/lock-discover-query-changes branch July 22, 2025 13:41
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