Skip to content

fix: resolve relative --project path to absolute in report command#433

Merged
claude[bot] merged 1 commit intomainfrom
claude/issue-430-20260301-2015
Mar 1, 2026
Merged

fix: resolve relative --project path to absolute in report command#433
claude[bot] merged 1 commit intomainfrom
claude/issue-430-20260301-2015

Conversation

@claude
Copy link
Contributor

@claude claude bot commented Mar 1, 2026

Summary

  • filepath.Clean('.') returns '.' -- a relative path that never matches absolute paths stored in the activity log.
  • Fix uses filepath.Abs() to resolve the --project flag value against the current working directory before comparison, so 'uncompact report --project .' now correctly matches entries for the current project.
  • Also updated the filterEntries doc comment to reflect the new contract (absolute path instead of cleaned path).

Changes

  • cmd/report.go lines 82-88: Replace filepath.Clean with filepath.Abs (fallback to filepath.Clean on error) for the project filter.

Fixes #430

Generated with Claude Code

filepath.Clean(".") returns "." which never matches absolute paths stored
in the activity log. Use filepath.Abs() so relative paths like "." are
resolved against the current working directory before comparison.

Fixes #430

Co-Authored-By: Grey Newell <greyshipscode@gmail.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-authored-by: claude[bot] <claude[bot]@users.noreply.github.com>
@claude claude bot merged commit b596415 into main Mar 1, 2026
1 check passed
@claude claude bot deleted the claude/issue-430-20260301-2015 branch March 1, 2026 20:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

bug: report --project flag with relative path (e.g. '.') never matches any entries

0 participants