Improve Tekton Object Interface
Open
@lcarva is already working on this.
Since Jul 20, 2023.
kind/feature
lifecycle/stale
- Dominant language
- Go
- Stars
- 277
- Forks
- 164
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 61
Description
As highlighted in https://docs.google.com/document/d/1IPE_xycMZ7I2ni98wPLFogY5xJEREdXuYwOuPnPL5Po/edit, when adding support for v1 objects, we need to replicate usage in a lot of files which is going to be tedious. We will need to keep support for v1beta1 around as well. It is unreasonable to keep two copies of all the functions that rely on v1beta1 types.
We use the tekton object interface quite a bit but its still not as heavily utilized in our formatting logic as it should be. This issue wants to investigate and improve the Tekton Object interface so that it can be utilized more heavily in our codebase.
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.
Assessment
This issue has not been assessed yet.