feat: Dashboards search

[kof]

Description

• Search the projects
• Use arrow keys directly from the search or by focusing the project
• Hit enter to open
• Empty state when nothing found

Steps for reproduction

1. click button
2. expect xyz

Code Review

• hi @kof, I need you to do
  • conceptual review (architecture, feature-correctness)
  • detailed review (read every line)
  • test it on preview

Before requesting a review

• made a self-review
• added inline comments where things may be not obvious (the "why", not "what")

Before merging

• tested locally and on preview environment (preview dev login: 0000)
• updated test cases document
• added tests
• if any new env variables are added, added them to .env file

[johnsicili]

1. On first login I see this bad layout, refresh works fine:

2. Why on the side? Header seems appropriate because what's below it is what you're filtering and tabbing after search would work. Right now tab after search goes to left nav. And it's just odd.. you look at projects, then want to filter so you go to a different panel.

3. I think related to the new login with secret, type 0000, hit enter, and enter selects Google instead of submitting the pass

[kof]

1. this background bug - I can't reproduce it any more, I saw it before and fixed it, but I am not sure how you are still getting it, seems like you are on the latest version and yet ....

[kof]

3. can't repro, hitting enter logs me in with pass ....

[kof]

2. The idea is to have a single search box for all things we are going to add over time, same as in figma

[kof]

Reagrding accessibility with tab - yeah not sure, next tabbable in line is navigation, but yeah after searching something you might want to tab into found items

[kof]

Actually just realized why The search position looks weird, its because I didn't show search results from all things, but just stayed in the same view, e.g. projects or templates.

The current position of search actually requires to show a new view, "search", which would show all things in one view. Not sure if I should move the search for now to the header or add the search view. Search view is better long-term.

[kof]

I think I am gonna add the search view now, its not hard.

[kof]

Another alternative could be using cmd+k interface here like we do in the builder, clicking on search would open cmd+k panel ....

[kof]

Hmm, problem is in this case search needs to either have all data loaded upfront or be done server-side.

[kof]

Hmm, ok I think I am going to do the following:

1. keep the search position
2. add the search view
3. keep the client-side search for snappiness (don't think its going to be too much data any time soon)
4. load both: starter templates list and projects on any route, so that its always available for the search
5. add the route for /search?q=abc