Closed v-xinda closed 11 months ago
@bwateratmsft We haven't touched this side of the extension, I'm thinking this could be related to the Docker Desktop update?
No, this "recently used" behavior is provided by the @microsoft/vscode-azext-utils package. Could be an update there busted it. We should investigate if the problem is widespread or just affecting contexts; if it's only contexts then it can definitely wait.
Okay sounds good.
@bwateratmsft It still works on Docker Images: Run
, so i think we should be okay. Is there any other command we should see if this works on?
I think I figured out what's happening. The underlying objects are changing--i.e. from "selected = false" to "selected = true"--so the hash code changes and recently used doesn't work. If you choose the same context several times in a row (even though to do so is redundant), it starts working again because the object doesn't change when it's already selected:
I think we can won't-fix since it using the same context over and over again isn't something users need to do.
OS: All Build Version: 20231012.1 Regression: Not a regression
Repro Steps:
Expect: There is a a label "recently used" next to the used context.
Actual: There is no label "recently used" next to the used context.
More Info: