Brandon Waterloo [MSFT]
Brandon Waterloo [MSFT]
This might have been a service issue.
I'd rather we did the work to get to partial support.
VSCode officially recommends doing both. Commands cannot be "hidden" from keyboard shortcuts, so it's basically always possible to execute a command, regardless of where it appears in the UI. So,...
I think this is a good candidate for un-stale'ing. :smile:
Related to https://github.com/dotnet/wpf/issues/1638.
@zsd4yr Our main use case is in VS so technically the problem doesn't apply to us directly (since we have the DesignTime target). My team works on the Docker tools...
One of our users hit this in https://github.com/microsoft/vscode-docker/issues/3553
The pinning to exactly 2.6.0 of `async` is preventing us in the Azure Account extension for VSCode from fixing this.
Could a class be created that takes `PagedAsyncIterableIterator` as a constructor parameter, and that exposes the necessary information? That would "hide" it from customers who don't need it, avoiding the...
> @bwateratmsft Unless the construct that took the iterator had some secret means of accessing associated page data, I'm not sure if I understand how that would work. Not saying...