Work on RFC 561 within the document to improve our drilldown features
Created by: Joelkw
It would be great to move forward with the needs described in RFC 561 because these tie into our use case flows for FY23 – from an insight, being able to see changes helps you fix vulnerabilities or follow up with whoever may have improved/worsened code health. I have added some relevant user quotes to the RFC.
I would like us to make sure this doesn't fall through the cracks and think we should track it in our iteration. A goal for this work would be if we end this issue with proposals that fit into the following categories:
- Iterations we could do to improve the drilldown experience now, based on our existing architecture 2. This includes purely frontend things, like displaying information on the page that is easy for us to fetch already!
- Things we would like to do but would not be possible to do right now without other foundational work, and the longer-term implications of drilldown features we can't do now, but would want to explore enabling – what foundational work would be required
- (This might be a dumb question, but) – in particular, I'd be curious to know if streaming search and/or compute endpoints would unlock any interesting drilldown UX to load things in real time rather than have to compute them ahead of time
Think of this as our normal user/design brief RFC process, but as an experiment and because engineers were excited about it, we're starting with some of the product/technical side rather than the product/design side.