Allow discovery of functions in nested directories

[kristof-mattei]

Folder setup:

src\trigger1\...
src\trigger2\...
...

I have modified the function.json files, however, every time I try to deploy the system tells me that there are no HTTP triggers found.

I think this is because the system is only scanning 1 folder deep.

vscode-azurefunctions/src/commands/deploy/notifyDeployComplete.ts

Line 60 in d1318ca

const children: AzExtTreeItem[] = await node.getCachedChildren(context);

Is there a different way of accomplishing this?

[ejizba]

This is actually a limitation of Azure Functions itself, not the VS Code extension. Here is the tracking issue: Azure/azure-functions-host#5373

Basically, the "function.json" files have to be one level away from the root of your project (where the "host.json" and "local.settings.json" files are). In the meantime, one option is to move "host.json" and "local.settings.json" into "src" as well.

[kristof-mattei]

@EricJizbaMSFT I'll give it a shot!

[AndrinGautschi]

Is there any progress on this issue? We'd like to have our nested folder structure at least while developing. Building an appropriate directory structure for deployment is no issue.

Edit: I figured out a workaround: Since we have to build /dist anyway, it works so far if we cd into the dist directory and func start there. It would be nicer tho if at least we'd have a --dir flag in the func start command. Thanks :)