-
Notifications
You must be signed in to change notification settings - Fork 137
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
Delete pkg package #300
Comments
+1000, we should also move anything that we don't intend to expose as a public API into one or more 'internal' packages |
@mmlb If no one is working on this, I can take a stab at this issue. |
@vigneshashokan I don't think anyone is working on it yet. I will assign the issue to you. Please take a read at the communication doc and do let us know if you face any issues in the slack channel. Looking forward to your contribution. 😄 |
@vigneshashokan I've done one part in #315 already. |
## Description Move workflow types and funcs out of pkg/ and into its own package. Also cleaned up some of the API and added some more validation while I'm here. ## Why is this needed Helps address #300 ## How Has This Been Tested? `go test` passes. ## How are existing users impacted? What migration steps/scripts do we need? Low impact. A bc-break is occurring here, but its in internalish code and no user is expected to be using this code. If they are `gofmt -w -r 'p.ParseYAML(b) -> p.Parse(b)' .` and removing the call to `ValidateTemplate` is all thats needed. ## Checklist: I have: - [ ] updated the documentation and/or roadmap (if required) - [x] added unit or e2e tests - [ ] provided instructions on how to upgrade
Stale issue. Some of this work is being addressed with an overhaul of the Tink repository anyhow. |
pkg packages is an anti pattern. Instead we should break out its contents into smaller/easier to use packages.
The text was updated successfully, but these errors were encountered: