Handle BOM validation errors #762
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Instead of displaying a generic error message for all responses with status code >= 400, display a human-readable error description when RFC 9457 problem details are returned. Signed-off-by: nscuro <[email protected]>
2 tasks
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Handles BOM validation errors as introduced in DependencyTrack/dependency-track#3522.
Instead of displaying a generic error message for all responses with status code >= 400, display a human-readable error description when RFC 9457 problem details are returned.
Addressed Issue
Relates to DependencyTrack/dependency-track#3218
Additional Details
Individual validation errors are returned by the API, but not currently displayed by the frontend. This is because multiple validation errors can be returned, and each error message can be rather long. We simply don't have the screen real-estate at the moment to display all of that.
Checklist
This PR introduces new or alters existing behavior, and I have updated the documentation accordingly