-
Notifications
You must be signed in to change notification settings - Fork 40.3k
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
change all PredicateFunc to use SelectionPredicate #30529
Conversation
ref: #29888 |
137c704
to
1c71477
Compare
registry unit test failing |
@smarterclayton |
return labels.Set{} | ||
// SelectableFields returns a field set that can be used for filter selection | ||
func SelectableFields(obj *extensions.ThirdPartyResourceData) fields.Set { | ||
return fields.Set{} |
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.
It would be more correct to return nil here to avoid an allocation. Selectable fields is read only, correct?
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.
Yes.
I had some thoughts on fields set:
- If no selectable fields, return nil
- An object has static selectable fields. We can store it someway.
Let me do the first one.
@smarterclayton |
GCE e2e build/test passed for commit eb516fb. |
@k8s-bot test this [submit-queue is verifying that this PR is safe to merge] |
GCE e2e build/test passed for commit eb516fb. |
Automatic merge from submit-queue |
What?
Why?
This change is