-
Notifications
You must be signed in to change notification settings - Fork 8.4k
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
Hiding a command by setting its name to null
doesn't work properly
#8402
Comments
@zadjii-msft - where was this filtering initially? During deserialization, or somewhere later on (in TerminalPage or Palette itself)? |
Oh man. I completely missed responding to this in the docs repo. My bad! @Don-Vito If you want to take a closer look at this, I'd guess the following places might be a good start: |
It is less likely that this is related to key bindings and more likely that it is related to not-key-bindings. |
@carlos-zamora - yep.. I looked there earlier today.. but didn't find any special treatment for name equals null.. neither in the latest version nor in the previous version.. so I was wondering if I am looking at the correct place or the filtering out done somewhere later on. |
@zadjii-msft , @carlos-zamora - on the de-serialization level I see a special handling for null only for action name, and not command name as appears in documentation. |
So, the hiding probably happens when we request the name and it comes back as |
When we request the name it might be too late to hide, because at this stage if the "name" didn't exist we will use the one generated from the args. I consider to take an older release and debug it. I just wondered if @zadjii-msft could possibly remember where this filtering was. |
Hey good call! Thanks for helping clean up the repo. /dup #7441 |
Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report! |
From MicrosoftDocs/terminal#189
The text was updated successfully, but these errors were encountered: