Idea
The extension keeps gaining features, some larger (color mode) and some not self-explanatory (column profile, freeze, range selection). A user currently has no way to learn what changed between updates or to discover features they would not stumble on by themselves. It would help to surface this inside the editor.
Options considered
1. "What's new" on update (preferred)
After an update, show a short release-notes view once. Compare the stored last version in globalState against the current package.json version and, on a bump, open a small webview or the changelog preview. Idiomatic in VS Code, reuses the CHANGELOG we already keep, runs once per update, not intrusive.
2. Walkthrough for non-obvious features
Use VS Code's built-in walkthroughs (contributes.walkthroughs) on the Get Started page. Optional, dismissible, one short step per feature with a GIF and a try-it button. Good fit for column profile, freeze and range selection.
3. Inline "new" hints with a Got it button
A small coach-mark on a new feature's button. Doable in the webview but the most intrusive option, so at most one subtle hint per release on the main feature, dismissed permanently. Not a pattern for every detail.
Direction
Start with option 1. Add a walkthrough later for the two or three features that really need explaining. Keep inline hints minimal or skip them. Quiet and optional over loud.
Idea
The extension keeps gaining features, some larger (color mode) and some not self-explanatory (column profile, freeze, range selection). A user currently has no way to learn what changed between updates or to discover features they would not stumble on by themselves. It would help to surface this inside the editor.
Options considered
1. "What's new" on update (preferred)
After an update, show a short release-notes view once. Compare the stored last version in
globalStateagainst the currentpackage.jsonversion and, on a bump, open a small webview or the changelog preview. Idiomatic in VS Code, reuses the CHANGELOG we already keep, runs once per update, not intrusive.2. Walkthrough for non-obvious features
Use VS Code's built-in walkthroughs (
contributes.walkthroughs) on the Get Started page. Optional, dismissible, one short step per feature with a GIF and a try-it button. Good fit for column profile, freeze and range selection.3. Inline "new" hints with a Got it button
A small coach-mark on a new feature's button. Doable in the webview but the most intrusive option, so at most one subtle hint per release on the main feature, dismissed permanently. Not a pattern for every detail.
Direction
Start with option 1. Add a walkthrough later for the two or three features that really need explaining. Keep inline hints minimal or skip them. Quiet and optional over loud.