Component Picker search isn't searching by component's name

Hey! Thank you for flagging this, I was able to reproduce with one of my component on my end.
Update: After checking on our backend, this is expected. In this case, our browser is searching for both components named "button" and components that visually resemble a button.

I’ve shared your feedback with our team since I understand how this can be confusing. Thanks again for bringing it up!

Hi, are there any updates on the issue? Still facing this problem every day. It’d be great if search would prioritize the components name and only then look for visual reference

FYI I was able to cheat this a bit by adding a description in my component. Like for the button, add “Button buttons” how many ways you can think of and it should show up more when you actually search Button.

Btw ​@Celine_ there’s also the issue that the sort looks completely random, and by that I mean when I look “select” in my Design systems file, the first 3 assets that come up are “Selection form”, “Calendar” and “Filter”.

If I search the same thing in my Design file, filtered to only show things from my Design system file, the first 3 assets that come up are “Selection form”, “Select” (what I was looking for), “Color selection”.

I understand it’s meant to look up components that look like “select”, but why is the result different between my 2 files when both search from the same library ?

Hey ​@Apolline , thanks for sharing these details ! The example you provided are very useful for understanding what you’re seeing!

I checked with the team, and one of the reasons for the different search results is that component search takes the context of the file you currently have open. As a result, assets from your Design System file may rank higher when you search inside that file, compared to searching from another file and applying the filter. This can lead to the variations you’re noticing in the top results, even though both searches use the same library.

I understand this can feel inconsistent, and your feedback is helpful for highlighting where the experience could be clearer. I’ve shared your notes with the team so they can keep this in mind as search continues to evolve.Thanks for reporting this!

Thank you for the explanation!