Skip to content

Conversation

@gggritso
Copy link
Member

@gggritso gggritso commented Nov 7, 2025

This component has a bunch of use, including via GlobalDrawer but no Scraps story! I'm about to do some work with it (supporting deferred rendering, and overspring padding) and it's a lot easier to do that in Scraps.

This felt like the right time to lift this component up in the folder hierarchy, too, and convert to a named export.

Does this component need any API changes or improvements before it's "official"? e.g., collapsed is awkward, passing className IMO is awkward, and so on

All other feedback welcome

@gggritso gggritso requested review from a team as code owners November 7, 2025 22:01
@linear
Copy link

linear bot commented Nov 7, 2025

@github-actions github-actions bot added the Scope: Frontend Automatically applied to PRs that change frontend components label Nov 7, 2025
@@ -0,0 +1,38 @@
---
Copy link
Member

Choose a reason for hiding this comment

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

Thank you @gggritso 🥇 Would you mind moving this inside a slideoverpanel folder and add an index.tsx with the exports? It's a convention we use for other files, and it avoids having to do import {SlideOverPanel} from '@sentry/scraps/slideoutpanel/slideoutpanel' which duplicates the component name

@JonasBa
Copy link
Member

JonasBa commented Nov 8, 2025

Does this component need any API changes or improvements before it's "official"? e.g., collapsed is awkward, passing className IMO is awkward, and so on

Definitely need some TLC, but I think it's a good start. Since I know you've worked on the transition config, wdyt about just making that sprint transition be the default? I don't even think we need or want to allow people to change that in this instance

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.

3 participants