Problem
Some parts of Gitbun currently assume Unix-style file paths (/), which can cause incorrect scope detection or analyzer behavior on Windows systems where paths use backslashes (\).
The project works fine on Linux/macOS in most cases, but path parsing logic should be made platform-safe so contributors and users on Windows get consistent behavior too.
This issue is mainly about reviewing places where paths are being manually split or normalized and replacing those with proper Node.js path utilities where needed.
A few likely areas to inspect:
- scope detection
- analyzer path parsing
- file grouping logic
- diff processing utilities
Using Node's built-in path module (path.sep, path.join, path.normalize, etc.) should solve most of the issues cleanly.
Problem
Some parts of Gitbun currently assume Unix-style file paths (
/), which can cause incorrect scope detection or analyzer behavior on Windows systems where paths use backslashes (\).The project works fine on Linux/macOS in most cases, but path parsing logic should be made platform-safe so contributors and users on Windows get consistent behavior too.
This issue is mainly about reviewing places where paths are being manually split or normalized and replacing those with proper Node.js path utilities where needed.
A few likely areas to inspect:
Using Node's built-in
pathmodule (path.sep,path.join,path.normalize, etc.) should solve most of the issues cleanly.