Click to code doesn't work when file has `(` inside the path
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- typescript
- Domain
- devtools
Research direction
Start by reproducing the click-to-code action with a file path containing (, using the reported React and TanStack Devtools versions. Trace how the editor command is assembled and verify the result by opening the reported AlertFilters.tsx location successfully.
Written by the indexing model from the issue text.
Description
TanStack Devtools version
0.4.1
Framework/Library version
React v18.2.0
Describe the bug and the steps to reproduce it
When I try to use the click to code function it doesn't work if there is a ( inside the file name, is it possible to add strings around the file name so that this works?
/usr/local/bin/cursor: eval: line 20: syntax error near unexpected token `('
/usr/local/bin/cursor: eval: line 20: `ELECTRON_RUN_AS_NODE=1 "/Applications/Cursor.app/Contents/MacOS/Cursor" "/Applications/Cursor.app/Contents/Resources/app/out/cli.js" -r -g /Users/archiekd/Developer/searchland/nx-monorepo/apps/web/src/pages/(dashboard)/alerts/_components/AlertFilters.tsx:27:9'
Could not open AlertFilters.tsx in the editor.
The editor process exited with an error: (code 1).
Your Minimal, Reproducible Example - (Sandbox Highly Recommended)
Path with ( inside it when using click to code
Screenshots or Videos (Optional)
No response
Do you intend to try to help solve this bug with your own PR?
No, because I do not have time to dig into it
Terms & Code of Conduct
- I agree to follow this project's Code of Conduct
- I understand that if my bug cannot be reliable reproduced in a debuggable environment, it will probably not be fixed and this issue may even be closed.
- Dominant language
- TypeScript
- Stars
- 499
- Forks
- 100
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 4
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from TanStack/devtools
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
Difficulty 3/5 1-2 days Newbie friendliness 74/100
All issues in TanStack/devtools
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
safetrustcr/dApp-SafeTrust#426 ·
-
area:workflow bug ready-for-agent
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
fil-donadoni/tolaria#4409 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Fission-AI/OpenSpec#1960 ·
-
Add dependabot Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
corsairdev/corsair#1764 ·