Ryan Albrecht

To start we should just flip the feature switch ( https://flagr.getsentry.net/#/flags/539) then we can remove the code afterwards

Hey @ZeusTheTrueGod, marking unsafe sections of code is a really interesting idea. I can remember similar situations that I've encountered where I know some statements are wonky and that flow...

First version implemented in https://github.com/getsentry/sentry/pull/54518 

### Update: You may notice that we shipped something very different from what is in the [figma](https://www.figma.com/file/BkgpCdPfr9AreSIUZLRrWk/Specs%3A-Tracing-Waterfall-View?type=design&node-id=29-14271&mode=design&t=w38JI2CU6CcsK0F3-0). I think though the new design solves all the problem statements which were...

We've delievered the Screenshots portion of this, but the annotations stuff has been deferred until we get some feedback. Unassigning and setting this back to TODO. Also renamed to better...

POC: https://github.com/getsentry/sentry-javascript/pull/11175

@gabsoftware I just merged https://github.com/getsentry/sentry/pull/74218 which I think will be the final thing to fix this. What was happening is that we have two paths to ingest feedback data, basically...

@AdrienFromToulouse i'll double check the docs around `show()`, and config override args to `createForm` or anything should be optional, so i'll look into that too. It might be a typescript...