Workspace packageCachePath with multiple paths not working

[SebastiaanLubbers]

I like having a workspace level .alpackages where the shared apps like base, system etc is placed. Then a project level .alpackages with apps that are specific for that project. Having the following code-workspace result in the new AL File Wizard not finding any objects

{
    "folders": [
        {
            "name": "My App 1",
            "path": "app1"
        },
        {
            "name": "My App 2",
            "path": "app2"
        },
        {
            "name": ".alpackages",
            "path": ".alpackages"
        }
    ],
    "settings": {
        "al.packageCachePath": [
            "../.alpackages",
            "./.alpackages"
        ]
    }
}

Related to #336 .

[rdebath]

I suspect that this is NOT because there are multiple alpackages paths. Instead it is because the directory that contains the .alpackages directory does not contain an extension. To get the lookup and the source download to work I have to make sure that the .alpackages directory is actually in a location that vscode will have started up the ALextension in.

NB: I don't use multiple paths, it's just that I was having the same issue with one shared .alpackages directory not physically inside any of the extension directories.