Playground search incorrect results

[sable]

It seems like the playground search functionality is no longer quite working as intended, I assume following the changes announced a few weeks ago:

New playground snippet search Release-Candidate

Hello dear people, For a long time we had a text-based search for the snippet server that was highly limited. There was no way to search for more than one keyword, filter results, or use advanced search mechanisms. On top of that, it was very slow! For the last few weeks I have worked on migrating the old snippet server to a brand new architecture. On top of simplifying our infrastructure, it also allowed me to generate an advanced search index based on all of our code snippets. Whenever you s…

The search type no longer seems to affect the results:

• Tags
• Code
• Name

all have the same search results, and most notably for the tags search, none of the returned results are tagged with the search term (“world”).

It also seems like code search itself is a bit hit and miss, for example (trying to match this pg):

• Searching for BABYLON.Engine.REPLACE yields no results
• Searching for BABYLON Engine REPLACE yields results with those terms anywhere in the playground

I’m also unsure if there’s a way to only return exact matches. This search returns two results that match exactly (including the playground above), and two that do not. (And again, oddly, searching for just the “MeshBuilder.CreatePlane” part of the above search yields no results).

[Cedric]

ping @RaananW

[RaananW]

@sable

The search type no longer seems to affect the results:

You know, I extensively tested that before deploying against the search index. However, I did not check it against the proxy server (which was not planned initially). And lo and behold, you are totally right.

I am deploying a new version right now that will fix the issue with the search field selection not working.

Regarding the second comment - first, the search index has no reference to the BABYLON namespace, so searching for BABYLON. would yield no results (or better yet - will be ignored). I’ll need to see why it doesn’t search MeshBuidler.CreatePlane correctly. It does search MeshBuilder .CreatePlane, so it seems like a small syntax issue (or an interesting indexing issue).
I have it assigned to me, i’ll run a few tests in the following days.