Replies: 1 comment
-
|
POC in #2167 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
1. Problem Statement
Current file path completion in Crush requires users to:
• Type the full path manually (error-prone, slow)
This creates a disjointed experience compared to modern shells like Fish, where Tab progressively completes into
directories without losing context.
Example:
@internal/uand highlightinternal/ui/utilusing the ARROW UP key2. User Story
3. Acceptance Criteria
AC1: Given I type @ and see completions, when I press Tab on a directory, then the path is inserted AND the menu stays
open showing that directory's contents.
AC2: Given I'm in continue mode after Tab, when I type additional characters, then the filter updates correctly treating
the full path (including slashes) as the query.
AC3: Given I see completions, when I press Enter, then the selection is accepted, the menu closes, and the file is
attached.
AC4: Given I Tab-complete a directory, when I continue typing, the completion menu remains open until I press Enter or
Escape.
Beta Was this translation helpful? Give feedback.
All reactions