VS Code: azurite.location enhancements
- Dominant language
- TypeScript
- Stars
- 2.3k
- Forks
- 393
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 36
Description
### Which service(blob, file, queue, table) does this issue concern?
All
### Which version of the Azurite was used?
3.11.0
### Where do you get Azurite? (npm, DockerHub, NuGet, Visual Studio Code Extension)
VS Code
### What's the Node.js version?
N/A
### What problem was encountered?
If `azurite.location` is set to a directory that doesn't exist, Azurite will fail to start with an `ENOENT` exception. I would argue that the extension should at least attempt to create the directory if it doesn't exist.
Additionally, it seems that tokens like `${workspaceFolder}` are not expanded. It would be nice to add support for these.
### Steps to reproduce the issue?
Set `azurite.location` to a directory that doesn't exist.
Add `${workspaceFolder}` somewhere in the `azurite.location` value.
### Have you found a mitigation/solution?
No.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.