VSCode extension should create and use .azurite folder in current working directory when no location is specified
- 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?
NA
### Which version of the Azurite was used?
v3
### Where do you get Azurite? (npm, DockerHub, NuGet, Visual Studio Code Extension)
NA
### What's the Node.js version?
NA
### What problem was encountered?
The default lcoaiton for azurite to create it's files is the current working directory when invoked from the vscode extension. This creates a bunch of files and folders, excessively polluting the workspace. It would be better to create a .azurite directory in the current directory and put all the required files in there. This folder can then be added to .gitignore and other ignore files.
It is not convenient to have to set the location to a fixed directory to reference a subfolder in the current working directory.
### Steps to reproduce the issue?
NA
### Have you found a mitigation/solution?
NA
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.