I'd like help if someone with styling experience wants to fix the issues with sizing / alignment between the button and filter field and the length of the text field itself. I'm trying to emulate the look and feel of the issue query bar on Github, for example:

Yay for the (scalable) backend implementation.

What should be/is the behavior if no term is provided? For example, if I just searched "ammario" and not "owner:ammario" what should happen?

Yay for the (scalable) backend implementation.

What should be/is the behavior if no term is provided? For example, if I just searched "ammario" and not "owner:ammario" what should happen?

Right now that's not implemented so it's just ignored. I want to make plain strings (no owner: prefix) to just do a search on workspace name, but that isn't supported on the backend yet.

I think that's right @f0ssel. The interesting thing is the search could be against the fully qualified workspace name, so you technically use that to search for owner as well.

@ammario I added this suggestion, why don't you take a look at this logic and let me know if you would expect different behavior: https://github.com/coder/coder/pull/1972/files#diff-46ce05d14402854a3999da903dcf3949351172316989f053196857f93fcc6d57R198-R229

@ammario I added this suggestion, why don't you take a look at this logic and let me know if you would expect different behavior: https://github.com/coder/coder/pull/1972/files#diff-46ce05d14402854a3999da903dcf3949351172316989f053196857f93fcc6d57R198-R229

That was a fun exercise of some of my older neurons. That LGTM! I'm excited to see this in action.

Will be getting some styling fixes in soon, but here's a demo of the current functionality:

I like the UX. The flicker is a bit jank, but I know you realize that too.

After some awesome styling work from @Kira-Pilot I think this is ready to merge, will be tagging for final reviews.

great job braving the FE!