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

Switch to more named errors (particularly in src/pkg) #11

Open
Racer159 opened this issue May 18, 2023 · 1 comment
Open

Switch to more named errors (particularly in src/pkg) #11

Racer159 opened this issue May 18, 2023 · 1 comment

Comments

@Racer159
Copy link
Contributor

Describe what should be investigated or refactored

We should prefer to use named errors in future features and should look through the code for places that we can standardize errors to be specific instantiations.

Links to any relevant code

https://github.com/defenseunicorns/zarf/blob/main/src/pkg/packager/create.go#L108

Additional context

This would help us be a better library to others and would help with unit tests.

@Noxsios
Copy link
Contributor

Noxsios commented Mar 7, 2024

imo this issue is too broad in scope + not very actionable.

Moving to defenseunicorns/pkg for a bit so the team is aware + can include this mentality as we build out the design docs for those libraries.

@Noxsios Noxsios transferred this issue from zarf-dev/zarf Mar 7, 2024
@Noxsios Noxsios moved this to Backlog in Zarf (old) Mar 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Status: Backlog
Development

No branches or pull requests

2 participants