You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
/v1/finding/project/{uuid} returns an object that doesn't include a URL to view the finding in the UI.
Proposed Behavior
Include a web-url field (or similar - I don't think there's precedent for this field name yet?) alongside the matrix that links to the frontend: http://{frontend}/projects/{project uuid}/findings/{component uuid}/{vuln uuid}.
It is already possible to build this URL from the matrix, but it's not obvious that this route exists - it isn't exposed in the UI in any way, so presenting it in the API response makes it much more usable.
This depends on frontend/#689 being merged for this URL to work.
The generic version of this enhancement is adding links to all of the relevant API responses: components, projects, vulnerabilities, policies, violations, etc. This specific one is the most impactful, as it's not easily discoverable via the frontend.
Maybe call it displayURI or something like that. The url field in an API response might be expected to point to the finding/entity "inside the API" instead of in "some frontend".
Current Behavior
/v1/finding/project/{uuid}
returns an object that doesn't include a URL to view the finding in the UI.Proposed Behavior
Include a
web-url
field (or similar - I don't think there's precedent for this field name yet?) alongside the matrix that links to the frontend:http://{frontend}/projects/{project uuid}/findings/{component uuid}/{vuln uuid}
.It is already possible to build this URL from the matrix, but it's not obvious that this route exists - it isn't exposed in the UI in any way, so presenting it in the API response makes it much more usable.
This depends on frontend/#689 being merged for this URL to work.
The generic version of this enhancement is adding links to all of the relevant API responses: components, projects, vulnerabilities, policies, violations, etc. This specific one is the most impactful, as it's not easily discoverable via the frontend.
Checklist
The text was updated successfully, but these errors were encountered: