frog log rejects Windows repository roots
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 265
- Forks
- 10
- PR merge metrics
- No merged PRs in 30d
Description
Expected Behavior
On Windows, frog log should use the repository root returned by Git as the local file-store root.
Current Behavior
Frog 1.1.0 resolves the Git root as C:/... but Store.file normalizes it to C:\\...; log then rejects the equivalent paths with STORE_ROOT_MISMATCH before writing an entry.
This reproduces in a clean checkout of the upstream frog@1.1.0 tag, so it is not specific to a consumer repository.
Possible Solution
Normalize context.resolve().root with Node's path.resolve before constructing and comparing the file store:
const root = path.resolve((await Git.root({ cwd })) ?? cwd)
Centralizing the normalization there also protects other commands that compare a file store root, including sync.
Minimal Reproducible Example
On Windows, clone Frog and run from its Git checkout:
frog list
frog log "Windows root comparison probe" --body "probe" --severity minor
Expected: a pending local entry is created.
Actual:
code: STORE_ROOT_MISMATCH
message: The injected file store must use the same root as `--cwd`.
The same result occurred with the official frog-windows-x64-baseline.exe v1.1.0 release binary and the v1.1.0 source entrypoint.
Context
Windows 11 x64. The Git root was observed as C:/..., while the Node file store root was C:\\... for the same directory.
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start at the source entry point where context.resolve uses Git.root, then inspect how Store.file normalizes and compares its root. Reproduce on Windows with the listed frog list and frog log commands; done means log creates the pending local entry without STORE_ROOT_MISMATCH, while other root comparisons such as sync remain consistent.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, node.js, typescript
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 78/100