Extension guidelines feedback #4270
Description
Feedback from the team:
- I feel the screenshots at the beginning are too small to fully see VSCode’s UI and correlate that to the labels used, maybe a more schematic version would help instead of the actual UI
- Notifications: I would add that an extension should always try to show progress in context and only use the global notification progress as last resort. in other words, if progress originates from a view, it should use that view location or editor if from the editor
- welcome views: using a tree for actions should be put to the “Don’ts”
- I wonder if this guide should be added into every extension that is generated via yo code as a way to advertise this better to extension authors Add section for extension guidelines vscode-generator-code#240
- https://code.visualstudio.com/assets/api/references/guidelines/notification-warning.png
If that diagnostics, then I’d say that’s a bad notification. We ship native UI to show errors in files and showing a notification that there are now diagnostics is really anti-platform IMO
