You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
This extension defaults to opening the output tab in the panel whenever a go test is run. This behavior should be configurable for a few reasons:
When the panel automatically opens (via outputChannel.show()), the terminal sometimes doesn't open fully (and instead does split screen). I'd prefer to update my keybinding for go.test.package to run go.test.package and then call toggleMaximizedPanel (using multi-command) to ensure the output tab always opens in full screen
I have tests that take a while and I want to stay in my editor while tests run
I have tests that I know work and I just want to see the coverage report in my code editor
Describe the solution you'd like
I think there are two approaches:
Provide supplementary commands for all test commands (e.g. go.test.packageandgo.test.packageAsync/Background)
Allow test commands to accept a keybinding args object that allows individual keybindings to specify background behavior (and possibly other testConfig in the future).
Describe alternatives you've considered
I can use the multi-command extension to run go tests, then close the panel, then open the maximized panel, but that is inconsistent (without a long delay), and is a bad user experience
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
This extension defaults to opening the output tab in the panel whenever a go test is run. This behavior should be configurable for a few reasons:
go.test.package
to rungo.test.package
and then calltoggleMaximizedPanel
(using multi-command) to ensure the output tab always opens in full screenDescribe the solution you'd like
I think there are two approaches:
go.test.package
andgo.test.packageAsync/Background
)args
object that allows individual keybindings to specify background behavior (and possibly other testConfig in the future).Describe alternatives you've considered
I can use the
multi-command
extension to run go tests, then close the panel, then open the maximized panel, but that is inconsistent (without a long delay), and is a bad user experienceAdditional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: