-
Notifications
You must be signed in to change notification settings - Fork 12
Undeprecate references #82
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
Conversation
embik
left a comment
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.
/approve
|
LGTM label has been added. Git tree hash: 7efee82c5bb28ec7e6aa44fa95b76cc39a9ce02c
|
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: embik 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 |
|
LGTM label has been added. Git tree hash: a7ec3cfb17ce08c02ed48bca3834f9a82ab26c28
|
Summary
References are still kind of useful and compact. In a future version we want to allow to configure related resources where 1 primary object can contain references to many related objects (but the admin only configures 1). Since Go templates only ever result in a string, references suddenly offer a new advantage: The ability to select and return multiple values at once.
What Type of PR Is This?
/kind documentation
Release Notes