Bug 426612

Description Mark Macdonald 2014-01-24 14:12:24 EST

Consider a library exporting a FooClient function that users can either invoke as a function (perhaps a constructor function, through `new) (1), or access as a member (2):

1)
> var lib = require("mylib");
> lib.FooClient() 

2)
> require("mylib").FooClient.connect("url");

> The Tern index might look like this (I think)
> {
>   "!define": {
>       "mylib": {
>           "FooClient": {
>               "!type": "fn()",
>               "connect": "fn(options : String)",
>               "prototype": {
>                  /* instance methods of FooClient would go here, if it had any */
>               }
>           }
>       }
>   }
> }

Currently when you trigger content assist on require("mylib"), we only propose FooClient() as a function call, not FooClient as a member. I expected to see both.

However, I only want to see the member proposal when FooClient has a non-default property defined on it (like connect() above). If FooClient had no interesting properties, I should only see the function-call proposal.

---------------
There's a concrete example of this in the mongodb index. "MongoClient" is supposed to be callable as a constructor but also has a static "connect()" function defined on it. But since MongoClient is not proposed as a member, the static connect() is not discoverable.