aws-amplify / aws-amplify/amplify-cli
Disable generation of VS Code ignore file when configuring project with VS Code editor
- Dominant language
- TypeScript
- Stars
- 2.9k
- Forks
- 825
- Avg merge
- 11d 23h
- Merged PRs (30d)
- 2
Description
**Is your feature request related to a problem? Please describe.**
Basically I want a user-level CLI option to disable #5321. Although I understand the value of a feature like this, especially for new developers to reduce cognitive load, I delete the file and `.vscode` directory every time it's added to my project.
It hides files such as `amplify/.config/local-aws-info.json`, which I need to occasionally access to fix Amplify issues such as [this one](https://github.com/aws-amplify/amplify-cli/issues/4952#issuecomment-677859508).
It's also nice to be able to quickly open `amplify/backend/amplify-meta.json` anytime to see stack information.
**Describe the solution you'd like**
A user-level CLI option to disable the file generated as a result of #5321.
**Describe alternatives you've considered**
Dealing with it and manually opening such files. (If I open the file `amplify/.config/local-aws-info.json` using Ctrl+P shortcut, then it will still appear in the editor despite the VS Code ignore rules)
Contributor guide
Research direction
Start by tracing the VS Code ignore-file generation introduced by #5321 and the CLI's user-level configuration handling. Check how the generated .vscode rules hide amplify/.config/local-aws-info.json and amplify/backend/amplify-meta.json; done means a documented CLI option prevents that file or directory from being generated without affecting other project setup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- cli, developer-experience
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100