Fix:issue#1216 allow the search filters to be cleared or reset to the default

[shubhit7]

Fixes #1216

• Change owner filter, from FormSelect to Select next component of patternfly alpha release. Old Select has been deprecated.
• Change the search field beside owner filter, from TextInput to SearchInput.

[shubhit7]

I figured out how we can use deprecated Select.
@KKoukiou Shall we use deprecated Select or Select Next ?

[KKoukiou]

I figured out how we can use deprecated Select. @KKoukiou Shall we use deprecated Select or Select Next ?

Either of the two works for now. Tending towards the deprecated one, so that we can move all Selects at once to the new.

[KKoukiou]

I am happy with the search input adoption - but totally disagree with adopting the typeahead for the system/user filter. Logs page uses the typeahead in a case where there are hunderds of select options, not 3 like here.
I know it's suggested in #1216 (comment) but it's just not correct design wise..

Please undo the select part, and keep the SearchInput. Let's also add a test for the new functionality and it's good to go.

[cockpituous]

These 2 added lines are not executed by any test. Details

[jelly]

PR looks good from my side but the tests fail everywhere, it looks like you will need to adjust how test for the value of the search input:

wait_js_cond(ph_has_val("#containers-filter","pod-1")): Uncaught (in promise) Error: #containers-filter does not have a value

[shubhit7]

PR looks good from my side but the tests fail everywhere, it looks like you will need to adjust how test for the value of the search input:

wait_js_cond(ph_has_val("#containers-filter","pod-1")): Uncaught (in promise) Error: #containers-filter does not have a value

You are right, using the SearchInput component changes the structure of dom elements compared to using simple TextInput component. Now the input box will be accessible by selector "#containers-filter input".

wait_js_cond(ph_has_val("#containers-filter input","pod-1")) should not throw any exception. I am not able to get hands on test suite setup.

[jelly]

PR looks good from my side but the tests fail everywhere, it looks like you will need to adjust how test for the value of the search input:

wait_js_cond(ph_has_val("#containers-filter","pod-1")): Uncaught (in promise) Error: #containers-filter does not have a value

You are right, using the SearchInput component changes the structure of dom elements compared to using simple TextInput component. Now the input box will be accessible by selector "#containers-filter input".

wait_js_cond(ph_has_val("#containers-filter input","pod-1")) should not throw any exception. I am not able to get hands on test suite setup.

To get the test running should be fairly easy:

TEST_OS=fedora-38 make vm
TEST_SHOW_BROWSER=1 ./test/check-application -vst TestApplication.testPods

[jelly]

Hey @shubhit7 do you still intend to work on this?