feat: surface extension and analyzer versions for issue reports - #68
Merged
Merged
Conversation
Users filing issues report the VS Code extension version when the version of the downloaded ALCops.Analyzers package is what actually matters. Make both versions easy to find and copy: - Add "ALCops: Copy Version Information" command that copies a ready-to-paste block (extension, analyzers + channel, AL Language, VS Code, OS, analyzers path) to the clipboard - Add "ALCops" output channel (LogOutputChannel) with a version banner on activation and after every install/update; route existing console.* logging through it - Enrich the status bar tooltip with extension, analyzers (with channel), and AL Language versions; text and click behavior unchanged Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
When users create an issue there's confusion about which version they are on: the VS Code extension has its own version, but most of the time the version of the downloaded ALCops.Analyzers NuGet package is what actually matters. That version is recorded in
.alcops-manifest.jsonbut surfaced nowhere persistent — the status bar shows only a count, there is no output channel, and version strings appear only in 5-second auto-dismissing toasts.Solution
Follows the pattern used by extensions with separately-versioned downloaded components (rust-analyzer, Python's language server, CMake Tools, C/C++):
ALCops: Copy Version Information— copies a ready-to-paste diagnostics block to the clipboard:LogOutputChannel) — version banner on activation and after every install/update; all existingconsole.*logging routed through it via a newsrc/logger.tsfacade (console fallback keeps pure-Node modules importable in vitest)ALCops: <n>text and click-to-select behavior are unchanged. Version info is cached and invalidated only on install oralcops.versionChannelchangesrc/version-info.tsis the single source of truth:gatherVersionInfo()plus pure formatters shared by the tooltip, clipboard block, and log banners. Handles AL extension missing, manifest missing/corrupt, and the pending-update'unknown'placeholder as "not installed".Notification wording and
.github/ISSUE_TEMPLATEare deliberately untouched.Testing
tests/version-info.test.ts), lint clean, typecheck clean, bundle builds🤖 Generated with Claude Code