Skip to content

fix: classify loose snapshots as generated output - #48

Merged
royalpinto007 merged 4 commits into
AgentPostmortem:mainfrom
Yurii201811:fix/loose-snapshot-classification
Sep 23, 2026
Merged

royalpinto007 merged 4 commits into
AgentPostmortem:mainfrom
Yurii201811:fix/loose-snapshot-classification

Conversation

@Yurii201811

Copy link
Copy Markdown
Contributor

What does this PR do?

I added a rule for loose .snap files, which were missed by the existing __snapshots__ directory rule. The scanner now includes them in trim totals and ignore patterns while keeping ordinary source unchanged.

Closes #41.

Checklist

  • Tests pass (node --test)
  • Updated docs / README if behavior changed
  • Added a CHANGELOG.md entry
  • Followed the existing code style

Notes

29 tests pass with Node 20.20.0, plus the fixture CLI JSON smoke. Both new regressions failed on unchanged main; they cover case handling, existing snapshot directories and scan totals.

I bumped the patch version as required and removed the existing conflict markers from package-lock.json while synchronizing its version. No runtime dependencies were added.

Prepared with assistance from Codex.

@royalpinto007
royalpinto007 merged commit 2d7f045 into AgentPostmortem:main Sep 23, 2026
1 check passed
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.

*.snap snapshot files classified as keep-source

2 participants