-
Notifications
You must be signed in to change notification settings - Fork 1.8k
SDK tool with an standard to report/output a list of errors. #3966
Copy link
Copy link
Closed
Labels
help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.kind/featureCategorizes issue or PR as related to a new feature.Categorizes issue or PR as related to a new feature.lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Milestone
Metadata
Metadata
Assignees
Labels
help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.kind/featureCategorizes issue or PR as related to a new feature.Categorizes issue or PR as related to a new feature.lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Feature Request
Describe the problem you need a feature to resolve.
The problem here is that instead of the command scorecard and bundle has a standard to return the result with a list of errors we have a different implementation to achieve the same for each command which reduces the maintainability as make it harder for who will consume the result via a pipeline for example.
See that the bundle validate uses the following implementation to return a list of errors in the project:
Then, another subcommand of the same bundle command, ( bundle run ), has another implementation done in the PR: #3908 to achieve the same.
Describe the solution you'd like.
So, IMO we should move the result implementation for internal/util and keep it a standard to output a list of errors.