You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale with a justification.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.
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 forv1beta1
around as well. It is unreasonable to keep two copies of all the functions that rely onv1beta1
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.
The text was updated successfully, but these errors were encountered: