-
Notifications
You must be signed in to change notification settings - Fork 29.3k
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
Handle errors from Dynamic Debug Configuration providers #202622
Handle errors from Dynamic Debug Configuration providers #202622
Conversation
If a Dynamic Configuration provider, via its method `provideDebugConfigurations`, returns `undefined` or throws an Error, the selector in the Debug Tab is left in a borked state instead of going back to the last selected item. This was initially reported in microsoft#198798, whose fix handled some cases, but not all. This commit attempts to handle all the remaining cases.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry it took so long to get to this. Thanks for the PR!
And you'll need to reply to the CLA bot. Not sure why it didn't show up before. |
@microsoft-github-policy-service agree company="Modular, Inc" |
@microsoft-github-policy-service agree company="Modular, Inc" |
@roblourens , thank you!! |
Thank you guys for the review!!! Happy to contribute with more debugging stuff. |
@roblourens , do you need to me to the rebase or will you manage that on your own? |
I'll take it from here, thanks |
If a Dynamic Configuration provider, via its method
provideDebugConfigurations
, returnsundefined
or throws an Error, the selector in the Debug Tab is left in a borked state instead of going back to the last selected item. This was initially reported in #198798, whose fix handled some cases, but not all. This commit attempts to handle all the remaining cases.The easiest way to test this, is to use a provider and return an Error from
provideDebugConfigurations
or returnundefined
and make sure that the Debug Tab selector is left unchanged.Related issue: #202623