Hide temp/ignore files prefixed with "." from file explorer

[rukiafarraj]

Expected Behavior

After launching edit in VS Code from AzureML, expect to not see nonstandard files prefixed with "." in file explorer view in VS Code

Actual Behavior

The system is generating a bunch of temp/nonstandard files and we're showing them in the file explorer when in VS Code. Editors like Jupyter/Jupyterlab hide these automatically for users. We're working to hide these in AML Studio too. For consistency, we should hide them in VS Code.

Steps to Reproduce the Problem

1. In an Azure Machine Learning workspace, with compute instance running
2. Navigate to Notebooks
3. Create a new notebook, notice some additional files will get created like ".amlignore" (working on a fix to hide these in the studio soon)
4. In the global toolbars, click "Edit in VS Code"
5. You'll notice when in VS Code, these files appear in the explorer (confusing to users and creates noise)

Specifications

• Version:
• Platform:

[tbombach]

Thanks for filing Rukia! This is a bit of a tricky issue, since users might want to edit their .gitignore files or .amlignore files while they're using the Compute Instance. Hiding them would help users who don't need to interact those files, but it would remove the functionality for users who do need them.

VS Code has a couple of ways of letting the user choose which files appear:

• https://stackoverflow.com/questions/31639563/filter-files-shown-in-visual-studio-code The user can change their settings to hide files using a wildcard pattern
• We could also work with the compute instance team to add a settings.json file to each CI that would direct VS Code on which files to exclude: https://code.visualstudio.com/docs/getstarted/settings#_settings-file-locations

[rukiafarraj]

Thanks, @tbombach for the review and response! I think the second option sounds ideal - what would it take?

For additional context, we've made changes on the AML side to hide files that start with "." in the studio, and Jupyter/lab does the same. For consistency, we should hide these when users go to VS code as well.