[Enhancement] Infer `dapr.yaml` when omitted from configuration
philliphoff opened this issue · 6 comments
If a Dapr task definition or debug launch configuration has been defined without an explicit run file, infer the dapr.yaml at the root of the workspace (if present). This will make creation/scaffolding of such configuration files simpler.
Hi, @philliphoff. Is that mean the local dapr.yaml file should be read by this extension and properties in this file needs to be filled in task.json and launch.json?
No, the suggestion is that, if the tasks.json and launch.json files omit the property that would normally point to the one and only dapr.yaml in the repo, the extension, when running the task and/or launching the debugger would simply assume that that dapr.yaml is the one to be used in the dapr run -f ... command. The .json files need not be changed. We're just saying that the user doesn't need to tell the extension (in the .json files) which file to use because the extension can figure it out at the time it actually needs to use it.