-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
feat: added multi-select for input parameters. Fixes #12017 #12579
base: main
Are you sure you want to change the base?
Conversation
4faa967
to
c5f865c
Compare
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.
Could you test the responsiveness of the multi-selection dropdown?
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.
I only took a quick look so far, but there is at least one problem that affects all of the codegen.
Yes, it seems there is no infrastructure for ui tests, is there a preferred way/tools to do that in this project? |
There's some unit tests, but no component, functional, or E2E tests for the UI. Although responsiveness is usually tested with visual tests, which are rarer these days too. Right now, we do a lot of manual testing for visual things, so a screenshot with your browser devtools set to a smaller screen would suffice for this.
i.e. this and attaching screenshots matches our current standards 👍 |
Added two more screenshots of 1024x768 screen size |
5b0ef28
to
f3b6eaf
Compare
@agilgur5 it seems that tests are a bit flaky, as at first all of them passed, but now each time I run, a different suite is failing. Can we rerun only the failing suites somehow? |
Bumping as no response for more than a week |
There was a recent flake that was fixed in #12596. It was hit very frequently, so a retry is not necessarily enough for that one. If you rebase, it should be fixed. I haven't had a chance to review several PRs in-depth yet due to my status, hopefully will get to the simpler ones soon as I recover |
Be safe, I had the same issue as well, hope you'll feel better soon. |
This comment was marked as resolved.
This comment was marked as resolved.
75aa9a9
to
bb0ac36
Compare
783955f
to
8fcec69
Compare
Signed-off-by: Uriah Ahrak <[email protected]>
Signed-off-by: Uriah Ahrak <[email protected]>
Signed-off-by: Uriah Ahrak <[email protected]>
Signed-off-by: Uriah Ahrak <[email protected]>
Hey again, I hope you are feeling better! I assume @sarabala1979 should look at it as well, so bumping just for a reminder! |
@agilgur5 Any news with that? |
Fixes #12017
Motivation
I made my changes, because in Argo Workflows UI we weren't able to use a dropdown as a multi-select, and instantiate the default value to something that is accepted by a multi-select component.
Modifications
Parameter
type, to include another field namedmulti
which is of type boolean. Only when we use the multi-select, we should make sure that themulti
value is being set totrue
, so the UI will treat the select box as a multi-select one, or either a single-select in case of a falsy-value.multi
value, and to plant the relevant callbacks to support the multi-select behavior, as I've seen that the UI library that argo uses already supports multi-select, it's just that no one used it.On Smaller Screen:
Verification
I saw that the UI doesn't have any kind of tests, so I manually checked that the functionality works in different screens that are using the parameters of type multi-select and single-select.