-
Notifications
You must be signed in to change notification settings - Fork 29k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Explore improving attach problem matcher UX #62937
Comments
The goal is to automatically attach problem matters when possible and let the user know that a problem matcher has been attached. For detecting whether there is a good problem matcher we can only check for problem matchers that we know might be applicable (ie, only typescript problem matchers in a typescript folder). There are two options for when we look for problems
The next questions are how we tell the user that there's a good problem matcher and whether we suggest the matcher of simply attach it. The original idea was to have a button near the terminal selector drop down and when a problem matcher is found, to decorate that button and not automatically attach the matcher. However, a new button is not universally celebrated and if there are split terminals a button won't make it clear which terminal the problem matcher goes to. Because of this it might make more sense to simply attach the problem matcher if we find one. Since this still needs to surfaced in the UI, we could put it in a silent notification. |
Closing the exploration. There will be a new item for what we actually decide to do with this. |
The UX that pops the quick pick ever time a task is run is to intrusive.
The text was updated successfully, but these errors were encountered: