Skip to content

Commit b441e2c

Browse files
authored
fix(issue-details): Avoid persisting stacktrace folding behaviour (#91719)
People have been closing them, coming back later and having trouble finding the stack trace. It's usually the most critical part of the debugging flow, so lets just always have it visible at the start. For some platforms though, they get long, so it can still be closed, but a refresh/page navigation will bring it back.
1 parent bbdeeff commit b441e2c

File tree

2 files changed

+2
-0
lines changed

2 files changed

+2
-0
lines changed

static/app/components/events/interfaces/threads.tsx

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -407,6 +407,7 @@ export function Threads({data, event, projectSlug, groupingCurrentLevel, group}:
407407
<InterimSection
408408
title={tn('Stack Trace', 'Stack Traces', threads.length)}
409409
type={SectionKey.STACKTRACE}
410+
disableCollapsePersistence
410411
>
411412
<Flex column gap={space(2)}>
412413
{threadComponent}

static/app/components/events/traceEventDataSection.tsx

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -349,6 +349,7 @@ export function TraceEventDataSection({
349349
type={type}
350350
showPermalink={!hasStreamlinedUI}
351351
title={title}
352+
disableCollapsePersistence
352353
actions={
353354
!stackTraceNotFound && (
354355
<ButtonBar gap={1}>

0 commit comments

Comments
 (0)