Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Standardize detector failure reporting and exception handling #1134

Open
4 tasks
Tracked by #1135
cobya opened this issue May 23, 2024 · 0 comments
Open
4 tasks
Tracked by #1135

Standardize detector failure reporting and exception handling #1134

cobya opened this issue May 23, 2024 · 0 comments
Assignees
Labels
breaking change Breaking change, requires major version bump .NET Pull requests that update .net code type:refactor Refactoring or improving of existing code

Comments

@cobya
Copy link
Contributor

cobya commented May 23, 2024

Across the various component detectors, there is a lack of standardized exception handling and error reporting via logger output. This leads to inconsistent user experience when detection for a specific ecosystem fails.

Tasks

This change will be released with other breaking changes planned for Component Detection v5. See tracking issue TBD.

@cobya cobya added .NET Pull requests that update .net code breaking change Breaking change, requires major version bump type:refactor Refactoring or improving of existing code labels May 23, 2024
@cobya cobya self-assigned this May 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking change Breaking change, requires major version bump .NET Pull requests that update .net code type:refactor Refactoring or improving of existing code
Projects
None yet
Development

No branches or pull requests

1 participant