feat: [M3-8883] - Use our search parser on Images Landing

[bnussman-akamai]

Description 📝

• Uses our search parser on the Images Landing page to provide users with slightly more flexibility 🔍
• This is just a "soft-launch". We can add user facing documentation as a follow up once we're confident in the feature and the API has had some time to improve filterability.

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/or size

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 (or tag 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 🧪

• Test various search queries on the Images landing page 🔍
• Verify the UI gracefully handles valid and invalid searches ✅ ❌

As an Author I have considered 🤔

• 👀 Doing a self review
• ❔ Our contribution guidelines
• 🤏 Splitting feature into small PRs
• ➕ Adding a changeset
• 🧪 Providing/Improving test coverage
• 🔐 Removing all sensitive information from the code and PR description
• 🚩 Using a feature flag to protect the release
• 👣 Providing comprehensive reproduction steps
• 📑 Providing or updating our documentation
• 🕛 Scheduling a pair reviewing session
• 📱 Providing mobile support
• ♿ Providing accessibility support

[github-actions]

Coverage Report: ✅
Base Coverage: 87.34%
Current Coverage: 87.34%

[abailly-akamai]

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)

[linode-gh-bot]

Cloud Manager UI test results

🔺 1 failing test on test run #6 ↗︎

❌ Failing	✅ Passing	↪️ Skipped	🕐 Duration
1 Failing	444 Passing	2 Skipped	101m 37s

Details

Failing Tests
	Spec	Test
❌	create-linode-region-select.spec.ts	Linode Create Region Select » region select

Troubleshooting

Use this command to re-run the failing tests:

yarn cy:run -s "cypress/e2e/core/linodes/create-linode-region-select.spec.ts"

[cypress]

Cloud Manager E2E    Run #6824

Run Properties:   Passed #6824  •  b40d5bd530: feat: [M3-8883] - Use our search parser on Images Landing (#11233)

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 ↗︎