-
Notifications
You must be signed in to change notification settings - Fork 263
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
Proposal: Introduce a "public" top-level package directory for sharing outside #889
Comments
ballot is over, all positive. Thanks ! /assign rhuss |
This issue is stale because it has been open for 90 days with no |
/remove-lifecycle stale |
This issue is stale because it has been open for 90 days with no |
/remove-lifecycle stale |
This issue is stale because it has been open for 90 days with no |
/remove-lifecycle stale |
@dsimansk I think we can close this issue but use it as an input for the new shared pkg repo structure ? |
@rhuss yep, works for me. |
Closing this and track it in #1039 |
Co-authored-by: Markus Thömmes <[email protected]>
One design goal of
kn
was also to expose a public API to offer common client functionality to other go based applications. We already have some of those API hooks but at various places:pkg/serving/v1
pkg/sources/v1alpha2
pkg/eventing/v1beta1
lib/test
pkg/kn/flags
This proposal suggests introducing a top-level package under which all externally shared code is collected.
This could be either the already exposed
lib
or maybe something more explicit likepublic
.Also, a CI test should check for whether any file of this directory is touched and raise some awareness (like an extra label) that a review should check for any backward compatibility issues.
Please add a 👍 for being positive for this change, 👎 if you against it.
The text was updated successfully, but these errors were encountered: