-
Notifications
You must be signed in to change notification settings - Fork 361
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: [M3-8883] - Use our search parser on Images Landing #11233
feat: [M3-8883] - Use our search parser on Images Landing #11233
Conversation
Coverage Report: ✅ |
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.
This is great and a nice improvement 🎉 Left comments that should be addressed, but are non-blocking.
- confirmed search parity with search filter and global search ✅
- confirmed error handling is sound ✅
My only concern in general with the feature (not so now, cause not only is it a parity item but a considerable improvement) is how can we communicate this feature to the user knowing that:
- every endpoint has its quirks and may or may not support a variety of filters, including filter operators
- every endpoint has its own handling of errors (sometimes we'll get a proper 400 with a message, sometimes a 500)
This is going to be an intricate UI and I wonder if we should start thinking of a util that's going to help us generate this contextual help, taking as arguments the things it can and can't do (with which we could also perhaps return our own errors)
packages/manager/src/features/Images/ImagesLanding/ImagesLanding.tsx
Outdated
Show resolved
Hide resolved
Cloud Manager UI test results🔺 1 failing test on test run #6 ↗︎
Details
TroubleshootingUse this command to re-run the failing tests: yarn cy:run -s "cypress/e2e/core/linodes/create-linode-region-select.spec.ts" |
Cloud Manager E2E Run #6824
Run Properties:
|
Project |
Cloud Manager E2E
|
Branch Review |
develop
|
Run status |
Passed #6824
|
Run duration | 24m 57s |
Commit |
b40d5bd530: feat: [M3-8883] - Use our search parser on Images Landing (#11233)
|
Committer | Banks Nussman |
View all properties for this run ↗︎ |
Test results | |
---|---|
Failures |
0
|
Flaky |
0
|
Pending |
2
|
Skipped |
0
|
Passing |
445
|
View all changes introduced in this branch ↗︎ |
* initial work * make overriding contains filter shape more generic * make things more generic * allow underscore in seaches * allow `:` in searches * only disable retries if the user is searching * add changeset * add changeset * use `errorText` prop @hana-akamai * add comment to summarize what is filterable --------- Co-authored-by: Banks Nussman <banks@nussman.us>
* initial work * make overriding contains filter shape more generic * make things more generic * allow underscore in seaches * allow `:` in searches * only disable retries if the user is searching * add changeset * add changeset * use `errorText` prop @hana-akamai * add comment to summarize what is filterable --------- Co-authored-by: Banks Nussman <banks@nussman.us>
Description 📝
Preview 📷
Search by
region
This will help power users using Image Service Gen2
Note
Sadly does not support complex operations (
+or
/+and
) due to API limitations. Only available in dev right now.Search by
label
and/orsize
Note
Because the API returns size in MB, the user would have to search in MBs 🫤 Planning to bring this to UX, but not blocking in my opinion
Search by
tags
(ortag
because it is aliased)Adds a sustainable way to filter by tag 🎉
Note
Searching by tag is partially broken. See
ARB-5792
How to test 🧪
As an Author I have considered 🤔