Closed eryc-cc closed 1 year ago
We need a "Search Results" box. We can use Radix UI for this since they already have accessibility figured out.
@pixelsbyeryc, don't know if I'm wrong on this one, but radix UI provides limited components with accessibility... and I'm not sure how to use in achieving a component not listed in their docs. Can you give more context on achieving this with radix?
@SunGoldTech I would use the same component that Radix uses to build their documentation search. If you type anything, you'll see the results. That's the type of navigation/functionality we want.
We're searching, and getting a list of results under a "dropdown"
@brandonroberts @0-vortex can Sunday use the dropdown menu to build it?
@SunGoldTech I would use the same component that Radix uses to build their documentation search. If you type anything, you'll see the results. That's the type of navigation/functionality we want.
We're searching, and getting a list of results under a "dropdown"
@brandonroberts @0-vortex can Sunday use the dropdown menu to build it?
My natural response is "sure" 🍕
Seems reasonable to me
In that case, I'll look into it 😎😎
:tada: This issue has been resolved in version 1.16.0-beta.13 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:
:tada: This issue has been resolved in version 1.16.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:
Summary
We need a "Search Results" box. We can use Radix UI for this, since they already have accessibility figured out.
Once the user types on the search input, the box will open to show the results.
Note: We might have different UI for each type of result, eg:
cc @SunGoldTech @brandonroberts
The Results scoped in this issue are for repositories, but we should allow other types of components to be added to the results.
Results States:
Props for Repository Results:
image
text
text
number
number
Preview: