Hi there
As I work on a Next.js application, I'm running into a path handling problem that seems to be more prevalent in Windows systems. I have organized route groups in my project, however CHADTree does not accept parenthetically enclosed routes correctly when I try to access files through them.
Description of Issue:
CHADTree opens an incorrect, empty file from a faulty path: app(routes)\car\page.tsx when it tries to open a file with the path app\(routes)\car\page.tsx. The way parenthesis in the path are handled seems to be the cause of this problem.
A Reference to a Related Problem:
This issue appears to be similar to a known Neovim Windows bug that is addressed here: Neovim Issue #24542, in which parenthetically enclosed file paths are treated incorrectly.
Hi there
As I work on a Next.js application, I'm running into a path handling problem that seems to be more prevalent in Windows systems. I have organized route groups in my project, however CHADTree does not accept parenthetically enclosed routes correctly when I try to access files through them.
Description of Issue:
CHADTree opens an incorrect, empty file from a faulty path:
app(routes)\car\page.tsxwhen it tries to open a file with the pathapp\(routes)\car\page.tsx. The way parenthesis in the path are handled seems to be the cause of this problem.A Reference to a Related Problem:
This issue appears to be similar to a known Neovim Windows bug that is addressed here: Neovim Issue #24542, in which parenthetically enclosed file paths are treated incorrectly.