Settings: add way to disable different modules/features
- Dominant language
- TypeScript
- Stars
- 2k
- Forks
- 807
- Avg merge
- 10h 12m
- Merged PRs (30d)
- 7
Description
It'd be nice if we could disable features if we feel that they aren't important for our workflows and/or don't work correctly because of lack of permissions. AWS has many different services for tons of different uses, so allowing the user to customize their experience just makes sense.
Having this configurable per-profile would be a huge plus, though a global solution could be acceptable if it's easy to manage.
Related:
* https://github.com/aws/aws-toolkit-vscode/issues/1244
* https://github.com/aws/aws-toolkit-vscode/issues/1433
* https://github.com/aws/aws-toolkit-vscode/issues/1585
* https://github.com/aws/aws-toolkit-vscode/issues/1823
Contributor guide
Research direction
Review the four related issues linked in the description first, then locate the extension's settings and profile configuration entry points; no files or tests are named here. Done means users can disable selected modules or features through a manageable global or per-profile configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, typescript, vscode
- Domain
- cloud, developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100