-
Notifications
You must be signed in to change notification settings - Fork 43
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
🐛 Use standard filters for languages in the Set Targets step #2045
Conversation
Resolves: konveyor#2009 Signed-off-by: Radoslaw Szwajkowski <[email protected]>
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #2045 +/- ##
==========================================
+ Coverage 39.20% 42.53% +3.33%
==========================================
Files 146 171 +25
Lines 4857 5504 +647
Branches 1164 1370 +206
==========================================
+ Hits 1904 2341 +437
- Misses 2939 3046 +107
- Partials 14 117 +103
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
- Track success status of both the `targets` and `tagCategories` queries - When they are both successful, then the pre-selection of targets providers based on application language tags can be done properly. - Use a `useEffect()` to do this here. It mostly works but will reset the selection to default if any of the related queries refetch. (Switch browser tabs and the fetches will run again when the application become visible again) Signed-off-by: Scott J Dickerson <[email protected]>
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.
There are a few things that could be done a bit different, but the biggest issue is actually when the initial selection is made. The targets and tag catagories may not have landed yet...and that makes the UI look strange for a few moments.
client/src/app/pages/applications/analysis-wizard/set-targets.tsx
Outdated
Show resolved
Hide resolved
client/src/app/pages/applications/analysis-wizard/set-targets.tsx
Outdated
Show resolved
Hide resolved
client/src/app/pages/applications/analysis-wizard/set-targets.tsx
Outdated
Show resolved
Hide resolved
Additional fetaures: 1. pre-fetch targets and tag categories to pre-filter targets 2. add error and loading handling Signed-off-by: Radoslaw Szwajkowski <[email protected]>
@sjd78
|
@sjd78 @ibolton336
Fun fact ....it's not the first time when I'm moving from card to table view :) Check out oVirt/ovirt-web-ui#1600 |
Assume the setting is optional and do not block the flow if missing. Signed-off-by: Radoslaw Szwajkowski <[email protected]>
…ter toolbar Signed-off-by: Radoslaw Szwajkowski <[email protected]>
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.
Looking really good. Mostly comments in the data hook.
client/src/app/pages/applications/analysis-wizard/set-targets.tsx
Outdated
Show resolved
Hide resolved
client/src/app/pages/applications/analysis-wizard/set-targets.tsx
Outdated
Show resolved
Hide resolved
client/src/app/pages/applications/analysis-wizard/set-targets.tsx
Outdated
Show resolved
Hide resolved
client/src/app/pages/applications/analysis-wizard/set-targets.tsx
Outdated
Show resolved
Hide resolved
client/src/app/pages/applications/analysis-wizard/set-targets.tsx
Outdated
Show resolved
Hide resolved
client/src/app/pages/applications/analysis-wizard/set-targets.tsx
Outdated
Show resolved
Hide resolved
Signed-off-by: Radoslaw Szwajkowski <[email protected]>
Optional queries failed during initial loadThe step loads correctly but lacks the features that depend on the optional queries:
After both queries are unblocked the screen loads the missing features. Screencast.from.2024-08-09.20-41-50.mp4Required query failedWithout the targets the step has no data to work on - however the user still may skip the step and continue to the next one. Screencast.from.2024-08-09.20-40-54.mp4 |
Signed-off-by: Radoslaw Szwajkowski <[email protected]>
@JustinXHale |
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
Before, in the Set Targets step, if the languages were not pre-selected automatically then no cards were visible. In order to see target cards user had to select at least one language. After this fix, all target cards will be visible. Additional changes: 1. wait (display a spinner) until all necessary queries finished before displaying Set Targets step 2. improve error handling 1. display error when targets could not be loaded 2. silently ignore failed optional queries and continue without extra featues 3. extract data fetching into one hook Resolves: #2009 Resolves: https://issues.redhat.com/browse/MTA-3515 --------- Signed-off-by: Radoslaw Szwajkowski <[email protected]> Signed-off-by: Scott J Dickerson <[email protected]> Co-authored-by: Scott J Dickerson <[email protected]> Signed-off-by: Cherry Picker <[email protected]>
…r#2045) Before, in the Set Targets step, if the languages were not pre-selected automatically then no cards were visible. In order to see target cards user had to select at least one language. After this fix, all target cards will be visible. Additional changes: 1. wait (display a spinner) until all necessary queries finished before displaying Set Targets step 2. improve error handling 1. display error when targets could not be loaded 2. silently ignore failed optional queries and continue without extra featues 3. extract data fetching into one hook Resolves: konveyor#2009 Resolves: https://issues.redhat.com/browse/MTA-3515 --------- Signed-off-by: Radoslaw Szwajkowski <[email protected]> Signed-off-by: Scott J Dickerson <[email protected]> Co-authored-by: Scott J Dickerson <[email protected]>
…2055) Before, in the Set Targets step, if the languages were not pre-selected automatically then no cards were visible. In order to see target cards user had to select at least one language. After this fix, all target cards will be visible. Additional changes: 1. wait (display a spinner) until all necessary queries finished before displaying Set Targets step 2. improve error handling 1. display error when targets could not be loaded 2. silently ignore failed optional queries and continue without extra featues 3. extract data fetching into one hook Resolves: #2009 Resolves: https://issues.redhat.com/browse/MTA-3515 --------- Signed-off-by: Radoslaw Szwajkowski <[email protected]> Signed-off-by: Scott J Dickerson <[email protected]> Co-authored-by: Radoslaw Szwajkowski <[email protected]> Co-authored-by: Scott J Dickerson <[email protected]> Signed-off-by: Cherry Picker <[email protected]>
Before, in the Set Targets step, if the languages were not pre-selected automatically then no cards were visible. In order to see target cards user had to select at least one language.
After this fix, all target cards will be visible.
Additional changes:
Resolves: #2009
Resolves: https://issues.redhat.com/browse/MTA-3515