Open flurbius opened 6 years ago
@flurbius it's because TypeSearch also uses a prop described as globals
from the search record (just g
in minified record) of typespublisher. And if you have a look at the globals of fusioncharts
you will see why it shows up, if you type in "treema":
{
"p": "http://www.fusioncharts.com",
"l": "fusioncharts",
"g": [
"FusionCharts",
"carbon",
"charts",
"fint",
"gantt",
"maps",
"ocean",
"powercharts",
"ssgrid",
"treemap",
"usa",
"widgets",
"world",
"zoomscatter",
"zune"
],
"t": "fusioncharts",
"m": [
// ...
],
"d": 0
},
It's because of "treemap". Not sure if the UI should somehow hint, why it's showing a package.
After the third or fourth attempt I finally got the search box to forget about what the autocomplete was telling it (fusioncharts) and accept what I typed (treema) and so actually searched for my package. (the secret was to type a space after my search term so while "treema" somehow matches "fusioncharts", "treema " doesn't.
However nothing showed up on the page so either TypeSearch is broken or there are no types defined for treema. Whatever the truth is - its out there - not here. Im sure whatever its doing is very clever but it shouldnt be masquerading as a search box.
Please show a zero result if thats what was returned - it matters. And dont substitute my text for something that is completely different.