Specify path for project

[wiecznyPoszukiwacz]

For our large project (about 7k files in multiple directories) I create small VS Code projects containing only needed directories. Unfortunatelly, Intelephense scans only those small directories when working with small projects.
It would be great, if I could define directory to scan (different from project directory), so Intelephense would provide definitions and symbols from whole project.

Example:
whole projects lays in c:/projects/system
I'm working with directory c:/projects/system/submodule

It would be great, if I could define

"intelephense.scanDir": "c:/projects/system"

in my c:/projects/system/submodule/.vscode/settings.json

to make Intelephense scan whole large project.

[bmewburn]

Thanks for the feedback. I agree that this would be very useful. File finding is currently provided by the vscode workspace api and there is talk of enabling multi folder workspaces. Will investigate further after the outcome of microsoft/vscode#396

[bmewburn]

In v0.8.0 I've made the extension compatible with the new multi root workspaces. It is experimental at this stage, let me know how it goes.

[Thijzer]

Hi, I don't think this is a a great idea. If I understand this correctly you wish to scope outside root dir. I think the strength of a good intellisense is keep true too the files from the autoloader.

[bmewburn]

@Thijzer can you add what the disadvantages are? This just enables users to structure their projects anyway they want. To find symbol definitions the workspace is scanned, any autoload functions or require expressions are not considered.

[Thijzer]

I would consider this unconventional thus I would not let it creep into my code.

It also might find more conflicting namespaces or files, duplications.
I would be better to symlink the core directory into your project vendor dir.

[bmewburn]

Closing this as I think multi-root workspaces has solved the issue.