-
-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Native stack traces: registers are hidden, button to show them is displaced #82641
Native stack traces: registers are hidden, button to show them is displaced #82641
Conversation
False as a value in dropdown was causing unexpected behaviour
This reverts commit ea6a831.
@@ -91,7 +91,6 @@ function NativeFrame({ | |||
isShowFramesToggleExpanded, | |||
isSubFrame, | |||
onShowFramesToggle, | |||
isExpanded, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should also be removed from the Props
type above. Any callsites that are passing it in will have to be updated as well.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I will take a look and make required changes for it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@nipunh Don't forget about cleaning up this extra prop in the types and callsites ^
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @ryan953, I have pushed the changes after clean this up.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@nipunh Please also delete line 63 from this file, the content is isExpanded?: boolean;
Then typescript should be happy, and we'll be all set!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All set!
grid-template-columns: auto 150px 120px 4fr repeat(3, auto) ${space(2)}; /* Adjusted to account for the extra element */ | ||
grid-template-rows: 1fr; /* Ensures a single row */ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I suspect that the grid columns will depend on the values of expandable
and hiddenFrameCount
. I will find some sample data to look at before I can know what to do here.
Also, the specific grid-column
and grid-row
css inside each *Cell
component seem like they're going to expect a specific number of columns, and two rows, if only at the small breakpoint.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the feedback, Once we have clarity from the data, I can help refine the grid logic further. Let me know your findings!
Just to make sure, I am on the right path here, The button (show/hide count) doesn't add a data column but instead adds an extra row header without a corresponding data column. This mismatch causes layout issues like pushing the ExpandCell to the next line.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks like it's supposed to go into two rows on purpose when the window is narrow. But the colunm widths in that case are kind of broken right now:
Can you re-test with a normal-width browser, and a narrow browser window, and share screenshots of the results.
I think you'll want to have something like grid-template-rows: repeat(2, auto);
with appropriate widths defined for the narrow @media breakpoint.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure, I will test and share the screenshots.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @ryan953
These are the screenshots for the existing code.
These are the screenshots after the change
I have also included the screen size in the screenshots.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
awesome! I wanted to see if stuff like that In App
tag was still moved down to the second row, looks like it is!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great! Is there anything else I can update here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@nipunh don't forget about that extra isExpanded
prop, we don't need it in the Props definition or at the callsites anymore.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, Verifying that and will push the changes soon.
removed unused Props from callsites that are passing it
…ub.com/nipunh/sentry into nipun/improvement/registers-are-hidden
…placed (#82641) <!-- Describe your PR here. --> Native stack traces: registers are hidden, button to show them is displaced #82371 1) Resolved the overflow issue 2) Always showing the "teaser" view of the registers initially ![Screenshot 2024-12-28 at 11 30 51 AM](https://github.com/user-attachments/assets/6aa8683b-cd11-4c77-b2c2-ed4ff4f25541) <!-- Sentry employees and contractors can delete or ignore the following. --> ### Legal Boilerplate Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.
Native stack traces: registers are hidden, button to show them is displaced #82371
Legal Boilerplate
Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.