Move shared code to knative/client-pkg
Open
Nobody has claimed this yet.
kind/refactor
triage/accepted
- Dominant language
- Go
- Stars
- 388
- Forks
- 274
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 8
Description
Since we have now knative/client-pkg for holding shared client code that can be used by kn but also plugins, we should move the client API to this repository (and while doing so, thinking about cleaning it up)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the client API currently used by kn and the shared-code expectations in knative/client-pkg. Map which parts are reusable by plugins and identify the cleanup scope before proposing changes. Done means the shared client API is moved to knative/client-pkg and remains usable by both kn and plugins.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100