You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometimes it's annoying, that the correct search result is not shown, just because the method or property that I am looking for, has the prototype keyword inside. For example, when I want to find get method from Map object, I will write: Map. to see all fields from Map and then start writing .g to see all fields starting with a g letter. At this point, all I can see are 4 search items, unrelated to my request.
I think it would be better, if the keyword prototype would be treated specially, allowing it to be omitted in such search requests.
The text was updated successfully, but these errors were encountered:
I agree that this is annoying. A workaround is to search for Map get with a space instead of a dot.
A simple solution would be to preprocess the search query by replacing . with . (or splitting at whitespace and before a dot), which would cause Map and .get to be treated as different query terms.
Sometimes it's annoying, that the correct search result is not shown, just because the method or property that I am looking for, has the
prototype
keyword inside. For example, when I want to findget
method fromMap
object, I will write:Map.
to see all fields fromMap
and then start writing.g
to see all fields starting with ag
letter. At this point, all I can see are 4 search items, unrelated to my request.I think it would be better, if the keyword
prototype
would be treated specially, allowing it to be omitted in such search requests.The text was updated successfully, but these errors were encountered: