Skip to content

Commit 4d82d94

Browse files
cursoragentclaude
andcommitted
fix(feature-info): Correct profiling link and list semantics
Use the org redirect profiling URL for the find-in-Sentry profile link to match existing docs patterns and avoid a potentially invalid destination. Render find-in-Sentry items as an ordered list so quick start locate-data steps keep their original numbered sequence. Co-Authored-By: Claude <noreply@anthropic.com>
1 parent 5b72cf8 commit 4d82d94

File tree

1 file changed

+5
-3
lines changed

1 file changed

+5
-3
lines changed

src/components/featureInfo.tsx

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -102,7 +102,7 @@ const FEATURE_DATA: Record<
102102
findInSentry: (
103103
<Fragment>
104104
Open the{' '}
105-
<ExternalLink href="https://sentry.io/profiling">
105+
<ExternalLink href="https://sentry.io/orgredirect/organizations/:orgslug/profiling">
106106
<strong>Profiles</strong>
107107
</ExternalLink>{' '}
108108
page, select a transaction, and then a profile ID to view its flame graph. For
@@ -158,8 +158,10 @@ type FeatureInfoProps = {
158158
* @param type - learnMore shows feature descriptions, findInSentry shows navigation help
159159
*/
160160
export function FeatureInfo({features, type}: FeatureInfoProps) {
161+
const ListTag = type === 'findInSentry' ? 'ol' : 'ul';
162+
161163
return (
162-
<ul>
164+
<ListTag>
163165
{features.map(key => {
164166
const feature = FEATURE_DATA[key];
165167

@@ -176,6 +178,6 @@ export function FeatureInfo({features, type}: FeatureInfoProps) {
176178

177179
return <li key={key}>{feature.findInSentry}</li>;
178180
})}
179-
</ul>
181+
</ListTag>
180182
);
181183
}

0 commit comments

Comments
 (0)