-
Notifications
You must be signed in to change notification settings - Fork 1.8k
TELCODOCS#2148: Usability improvements in cluster-compare plugin #91033
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
base: main
Are you sure you want to change the base?
Conversation
@lack |
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
3ec8b17
to
b36e460
Compare
b36e460
to
5379cca
Compare
/lgtm |
/label peer-review-needed |
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.
2 minor comments; LGTM
5379cca
to
b6939a3
Compare
New changes are detected. LGTM label has been removed. |
b6939a3
to
5842ef2
Compare
6561625
to
3095932
Compare
|`toYaml` | ||
|Renders incoming data as YAML while preserving object types. | ||
|
||
|`doNotMatch` |
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.
Perhaps we should have an example like we do for lookupCRs
so that the syntax is clear and we've got similar format for all three of these custom functions?
Example:
{{ if $condition }}{{ doNotMatch $reason }}{{ end }}
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! That works too!
For now I have added the above example that you have shared!
If there is an example similar to lookupCR, could you please here? @lack
3095932
to
e4b8e50
Compare
@sr1kar99: all tests passed! Full PR test history. Your PR dashboard. 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-sigs/prow repository. I understand the commands that are listed here. |
/lgtm |
@dgonyier: changing LGTM is restricted to collaborators In response to this:
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-sigs/prow repository. |
Requesting another round of peer review because of some updates! /label peer-review-needed |
Version(s):
4.19
Issue:
TELCODOCS-2148
Link to docs preview:
QE review: