-
Notifications
You must be signed in to change notification settings - Fork 266
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
Retrurn error if exist duplicate key in filter option #575
Conversation
Hi @MIBc. Thanks for your PR. I'm waiting for a knative member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/ok-to-test |
The following is the coverage report on the affected files.
|
/retest |
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.
/lgtm
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: MIBc, navidshaikh 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 |
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.
thanks, looks good to me !
While we are at it: both methods you changed have quite some overlap. I would prefer to have a single method, which takes another boolean parameter, whether to check for filters to delete. Thinking again, we could even keep the removal of types even for create as a no-op, as you can't easily use filter key with a trailing dash anyway (how would you update those ?). So we could keep a single method for both create & update.
Would you mind to combine these two methods already within this PR ?
or then maybe in a next PR ;-) |
(was too slow ...) |
Sure, I will do. |
Yes. I will try. Thanks! |
Based on the feedback for the tool, this change addresses: 1. Wrapping JSON like display inside a HTML page and color code covered(green) and notcovered(red) fields for better readability. 2. Fixes the total field calculation by taking into account ignored fields. 3. Ensures we visit a node type only once and prune the traversal if a same node type appears again in other parts of resource tree.
Fixes #569
Proposed Changes
*Return error if user set duplicate key in
--filter
option. For example,kn trigger create --filter type=bla --filter type=blub test
.