bug: "resource" vs. "object" confusion in apis/apis #2922
Labels
area/apiexports
kind/bug
Categorizes issue or PR as related to a bug.
lifecycle/rotten
Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Describe the bug
The general rule in Kubernetes code is that the word "resource" means a kind or type of API object rather than an individual one, while the word "object" is used when an individual API object is meant. I know this is surprising to outsiders, since HTTP defines a "resource" to be anything with a URL or URI. But it is a convention that is fairly strongly followed in the Kubernetes code base (sadly, less so in the user-facing documentation), and it would help to continue following it here.
Following are some places that currently use the word "resource" where individual API objects are meant.
kcp/pkg/apis/apis/v1alpha1/types_apiexport.go
Line 205 in 5897550
kcp/pkg/apis/apis/v1alpha1/types_apiexport.go
Line 213 in 5897550
kcp/pkg/apis/apis/v1alpha1/types_apiexport.go
Line 224 in 5897550
Steps To Reproduce
Read the docs
Expected Behaviour
Terminology consistent with the predominant usage in Kubernetes code.
Additional Context
No response
The text was updated successfully, but these errors were encountered: