| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
- Extract command registration logic from UnitTestManagementService into standalone registerTestCommands function - Call registerTestCommands synchronously in activateLegacy before async operations - This ensures commands are available immediately when extension activates, preventing "command not found" errors Co-authored-by: eleanorjboyd <26030610+eleanorjboyd@users.noreply.github.com>
…vation - Register test services (unitTestsRegisterTypes) before any async operations in extension.ts - Register test commands immediately after service registration, before experimentService.activate() - Remove duplicate registrations from extensionActivation.ts activateLegacy() - This ensures commands are available synchronously when extension activates Co-authored-by: eleanorjboyd <26030610+eleanorjboyd@users.noreply.github.com>
| Back | FazBrowse Home | New Git URL |
fixes #22783 and #21865
The python.configureTests command was registered after multiple async operations during extension activation, creating a race condition where users could invoke the command before it was registered.
Changes
Extract command registration: Created standalone registerTestCommands() function in testing/main.ts containing all test command handlers (Tests_Configure, Tests_CopilotSetup, CopyTestId)
Register synchronously before first await: Moved unitTestsRegisterTypes() and registerTestCommands() to extension.ts immediately after initializeStandard(), before experimentService.activate()
Remove duplicate registrations: Cleaned up original registration in UnitTestManagementService.activate() and activateLegacy()