jest + tab does not show a list of files in the current directory

Open
#2,344 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
rust, zsh
Domain
cli

Research direction

Start by reproducing the completion behavior in Warp with yarn test and jest in a directory containing the listed test files, using the reported macOS and zsh context. Trace the command completion entry point and existing cd completion behavior; done means Tab lists the matching files without regressing other completions.

Written by the indexing model from the issue text.

Description

area:window-tabs-panes bug ready-to-implement triaged
Discord username (optional)

No response

Describe the bug

Pressing tab after entering yarn test or jest does not show a list of files in the current directory.

// folder structure

__tests__
  someTest1.test.ts
  someTest2.test.ts
// in Warp

__tests__ 
yarn test // pressing Tab after this does not show a list of files in __tests__
To Reproduce

N/A. I can not share company code.

Expected behaviour

Pressing tab after yarn test or jest should show someTest1.test.ts and someTest2.test.ts.
This behavior exists on Mac's Terminal (zsh). This behavior also exists in Warp for cd commands.

Screenshots

No response

Operating System

MacOS

OS Version

13.0 Beta

Shell Version

zsh: 1.73.1 6261075646f055b99068d3688932416f2346dd3b arm64

Warp Version

v0.2022.12.06.08.03.stable_01

Additional context

No response

Does this block you from using Warp daily?

Yes

Warp Internal (ignore): linear-label:b8107fdf-ba31-488d-b103-d271c89cac3e

None

Dominant language
Rust
Stars
65.1k
Forks
5.6k
PR merge metrics
PR metrics pending

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from warpdotdev/warp

All issues in warpdotdev/warp

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.