Generic Schema (FE): Define Vuln Details Display Schema
Why are we doing this work
Part of delivering the parent Epic's expected outcome item 4 is to render the UI of the Vulnerability Details page in the style defined according to mock ups in the design issue . In order to do this, the backend will need to deliver the vulnerability data in an expected, agreed upon format.
This display report schema, henceforth known as the Vuln Details Display Schema, facilitates the dynamic display of the components based on the data associated with a vulnerability. This issue represents the work required to define that schema based on the requirements defined in the [design issue](design issue #267193 (closed))
Implementation plan
The frontend and backend needs to agree on a Schema, which will be consumed by the frontend to display a list of dynamic components. The list of components can be found here. All these components are already present in our GitLab UI library, therefore we just need to check what properties they expect in order to render the content and ask the backend to provide these details in the agreed schema.
This issue is not about writing code, rather, it's about collaboration with the backend. The person who is assigned this task should create a JSON schema and let the backend know what we expect. Later, once the schema is ready, we'll need to write code in (#285144 (closed)), in order to parse this schema and display the components listed here #267193 (closed).