project_panel: Always open panel on pane's reveal in project panel#53539
project_panel: Always open panel on pane's reveal in project panel#53539
Conversation
Update the way `pane::RevealInProjectPanel` is handled to ensure that, regardless of whether the file belongs to any open project, the project panel is always activated and focused. This refactor is a result of some internal feedback after changing its handling so as to show a notification stating that the item that the user was trying to reveal didn't belong to an open project. We feel users are probably already used to relying on `cmd-shift-e` (on macOS), in pretty much every context, in order to open the project panel, and so having situations where it doesn't actually happen seems like a bad user experience.
|
Does this need to be cherry-picked to stable? The stable release notes mention this PR, but it isn't part of the release. Ideally, this should've landed in the same release as #51246. |
Definitely! Thank you for calling that out, I had a note to cherry pick to preview right after merging but somehow forgot to do that 🤦 Will coordinate with the team to see if it makes sense to do a patch release including this, and likely other changes. Thanks! |
|
/cherry-pick stable |
|
/cherry-pick preview |
…53539) Update the way `pane::RevealInProjectPanel` is handled to ensure that, regardless of whether the file belongs to any open project, the project panel is always activated and focused. This refactor is a result of some internal feedback after changing its handling so as to show a notification stating that the item that the user was trying to reveal didn't belong to an open project – #51246 . We feel users are probably already used to relying on `cmd-shift-e` (on macOS), in pretty much every context, in order to open the project panel, and so having situations where it doesn't actually happen seems like a bad user experience. Relates to #23967 Release Notes: - Improved `pane: reveal in project panel` to open the project panel, even if working with an unsaved buffer.
|
🍒💥 Cherry-pick did not succeed |
We're doing another preview release today to get our latest parallel agents features out there. This PR is a rollup of all the changes we need to cherry pick. - [x] 7a26e48 from #54081 - [x] #54066 - [x] #53992 - [x] #54079 - [x] #54057 - [x] #54056 - [x] #54052 - [x] #53999 - [x] #54009 - [x] #53539 (already cherry picked as 25e02cb) - [x] #54070 - [x] #54053 - fix `run_tests.yml`: 67e92b5 - [x] #53979 - [x] #53884 - [x] #54067 - [x] #54014 (already on branch) - [x] #54030 (already on branch) - [x] #54094 Release Notes: - N/A --------- Co-authored-by: Lukas Wirth <me@lukaswirth.dev> Co-authored-by: Bennet Bo Fenner <bennet@zed.dev> Co-authored-by: Nathan Sobo <nathan@zed.dev> Co-authored-by: Ben Brandt <benjamin.j.brandt@gmail.com> Co-authored-by: Bennet Bo Fenner <bennetbo@gmx.de> Co-authored-by: Danilo Leal <67129314+danilo-leal@users.noreply.github.com> Co-authored-by: Neel <neel@zed.dev> Co-authored-by: Richard Feldman <richard@zed.dev>
…ed-industries#53539) Update the way `pane::RevealInProjectPanel` is handled to ensure that, regardless of whether the file belongs to any open project, the project panel is always activated and focused. This refactor is a result of some internal feedback after changing its handling so as to show a notification stating that the item that the user was trying to reveal didn't belong to an open project – zed-industries#51246 . We feel users are probably already used to relying on `cmd-shift-e` (on macOS), in pretty much every context, in order to open the project panel, and so having situations where it doesn't actually happen seems like a bad user experience. Relates to zed-industries#23967 Release Notes: - Improved `pane: reveal in project panel` to open the project panel, even if working with an unsaved buffer.
Update the way
pane::RevealInProjectPanelis handled to ensure that, regardless of whether the file belongs to any open project, the project panel is always activated and focused.This refactor is a result of some internal feedback after changing its handling so as to show a notification stating that the item that the user was trying to reveal didn't belong to an open project – #51246 .
We feel users are probably already used to relying on
cmd-shift-e(on macOS), in pretty much every context, in order to open the project panel, and so having situations where it doesn't actually happen seems like a bad user experience.Self-Review Checklist:
Relates to #23967
Release Notes:
pane: reveal in project panelto open the project panel, even if working with an unsaved buffer.