[go: nahoru, domu]
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.

Sign up for GitHub

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

Jump to bottom

Aggregate errors in package parsing #301

Open
hasheddan opened this issue Nov 1, 2021 · 2 comments
Open

Aggregate errors in package parsing #301

hasheddan opened this issue Nov 1, 2021 · 2 comments
Assignees
@hasheddan
Labels
enhancement New feature or request wontfix This will not be worked on

Comments

@hasheddan
Copy link
Member

What problem are you facing?

Currently, the package parser will return with error as soon as it encounters an issue. This means that a user building a package with multiple errors will have to fix each issue one by one and rebuild to see if the package is well-formed between each step.

How could Crossplane help solve your problem?

The package parser should identify all errors and aggregate them so that users both building and installing packages can have a comprehensive view of all errors that must be corrected.
@hasheddan hasheddan added the enhancement New feature or request label Nov 1, 2021
@hasheddan hasheddan self-assigned this Nov 1, 2021
@negz
Copy link
Member
negz commented Dec 1, 2021

@hasheddan Any thoughts on how we'd present an aggregated array of errors cleanly? iirc there's a couple of different places in which we'd return these - e.g. kubectl crossplane, revision events, etc?

@stale
Copy link
stale bot commented Aug 13, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix This will not be worked on label Aug 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@hasheddan hasheddan

Labels
enhancement New feature or request wontfix This will not be worked on
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@negz @hasheddan