-
Notifications
You must be signed in to change notification settings - Fork 14.6k
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
fix an offense against the style guide. #13835
Conversation
ptux
commented
Apr 16, 2019
> Refer to API objects without saying “object,” unless omitting “object” leads to an awkward construction.
/assign @bradtopol |
Deploy preview for kubernetes-io-master-staging ready! Built with commit 8dc42b9 https://deploy-preview-13835--kubernetes-io-master-staging.netlify.com |
@@ -66,7 +66,7 @@ In the `.yaml` file for the Kubernetes object you want to create, you'll need to | |||
You'll also need to provide the object `spec` field. The precise format of the object `spec` is different for every Kubernetes object, and contains nested fields specific to that object. The [Kubernetes API Reference](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/) can help you find the spec format for all of the objects you can create using Kubernetes. | |||
For example, the `spec` format for a `Pod` object can be found |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For consistency can you fix the Pod object as well?
Hi @ptux thank you for your contribution. Can you fix the Pod object as well that is right above for consistency? See my inline comment. Thanks |
Actually, @ptux looking at the context I believe leaving in object helps to clarify the association between Pod and Deployment being object types. So I am inclined to leave in object as it provides clarity. |
In that kind of meaning, we should change the style guide. |
It's a borderline case but it reads ok with with object removed. So let's go with the style guide. I'll merge it. Great job! |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bradtopol The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Thank you. In my opinion, in the Kubernetes world, user should understand |
Agreed! |
* fix an offense against the style guide. > Refer to API objects without saying “object,” unless omitting “object” leads to an awkward construction. * fix another one.
* fix an offense against the style guide. > Refer to API objects without saying “object,” unless omitting “object” leads to an awkward construction. * fix another one.