-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
3
-
Iteration C (May 19 - May 30), Iteration D (June 2 - June 13), Iteration E (Jun 16 - 30), Iteration F (Jun 30 - Jul 14)
-
None
-
Developer Tools
Our filtering can be improved further if we first see if there are any property/method kind completions and then just use those, then if there aren't return all completions.
The reason is that db.test.find({m makes it through this filter and then you get all globals starting with m anyway. But to properly solve it we need more context.
ie. if you're after { (ie. inside an object literal) and you're to the left of a : (or there isn't one) then you probably don't want globals regardless. If you're to the right of a : it is probably fine because you could be using a variable.