-
Notifications
You must be signed in to change notification settings - Fork 492
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
Rename ParentRef to be consistent with other reference types. #982
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jpeach 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 |
Across the API, the object reference types are all called `FooBarReference`. To be consistent with this pattern, `ParentRef` should be called `ParentReference`. Signed-off-by: James Peach <jpeach@apache.org>
d339674
to
f510f74
Compare
LGTM. |
Thanks! /lgtm |
`ParentRef` -> `ParentReference`, as per kubernetes-sigs/gateway-api#982.
`ParentRef` -> `ParentReference`, as per kubernetes-sigs/gateway-api#982.
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Across the API, the object reference types are all called
FooBarReference
. To be consistent with this pattern,ParentRef
should be called
ParentReference
.A few issues with this PR
Which issue(s) this PR fixes:
N/A
Does this PR introduce a user-facing change?: