Support mode where only the root of a project tree is dumped and not it referenced projects

[dbaeumer]

The vertex in question:

{"id":3,"type":"vertex","label":"document","uri":"file:///c:/Users/dirkb/Projects/mseng/VSCode/lsif-node/samples/typescript-ref/shared/src/provide.ts","languageId":"typescript","contents":"ZXhwb3J0IGZ1bmN0aW9uIGFkZChhOiBudW1iZXIsIGI6IG51bWJlcik6IG51bWJlciB7DQoJcmV0dXJuIGEgKyBiOw0KfQ=="}

[dbaeumer]

Actually the dump is OK since the lsif-tsc create the information for the client project and the shared project, since the client depends on shared. If you look at how the client code depends on shared then you see that the dependency is correctly made to the provide.d.ts. The corresponding vertex is:

{"id":64,"type":"vertex","label":"document","uri":"file:///c:/Users/dirkb/Projects/mseng/VSCode/lsif-node/samples/typescript-ref/shared/out/provide.d.ts","languageId":"typescript","contents":"ZXhwb3J0IGRlY2xhcmUgZnVuY3Rpb24gYWRkKGE6IG51bWJlciwgYjogbnVtYmVyKTogbnVtYmVyOw0KLy8jIHNvdXJjZU1hcHBpbmdVUkw9cHJvdmlkZS5kLnRzLm1hcA=="}

The dump also correctly contains two moniker definitions for the provider#add method. These are for the src/provide.ts in shared

{"id":49,"type":"vertex","label":"moniker","kind":"export","scheme":"tsc","identifier":"../shared/out/provide:add"}
{"id":50,"type":"edge","label":"moniker","outV":10,"inV":49}

and these for out/provide.d.ts referenced from client

{"id":158,"type":"vertex","label":"moniker","kind":"import","scheme":"tsc","identifier":"../shared/out/provide:add"}
{"id":159,"type":"edge","label":"moniker","outV":156,"inV":158}

So I think what is missing is that we provide a mode for the lsif-tsc tool to only dump the active / root project and not its dependent projects.

[dbaeumer]

@BertanAygun See my comments above.

[BertanAygun]

I agree having such a switch would be great in LSIF tools since knowing if a file actually belongs to a project or not may be something LSIF tool caller does not about since it would be language specific information.

Ideally, LSIF output involving multiple projects would actually be distinct trees only joined by moniker vertices. Although I understand that there are some cases where files are shared such as 2 projects importing the same code file by path reference instead of project reference.

[dbaeumer]

OK. I updated the title accordingly.