fix: standardize JSON file path key to 'path' across all commands
Every command that emits a file path in JSON output now uses 'path'. Previously content-grep used 'file', code cat used 'file_path', core cat used 'file_path', breakage used 'file_path', dead used 'file_path'.
Commands fixed: - content-grep: results[].file → results[].path - code cat: results[].file_path → results[].path - muse cat: file_path / files[].file_path → path / files[].path - code breakage: issues[].file_path → issues[].path - code dead: results[].file_path → results[].path
1081 tests green.
sha256:5d08a394a0ba78a4d517e40052ea84a2c57e82da0fbb3c73f59cc21ba1497def
sha
+3
~45
−3
symbols
sha256:c18fff91c10f549de3f15fb6989c1ae628796bd84c66cb986f4fe528d56ca5eb
snapshot
+3
symbols added
~45
symbols modified
−3
symbols removed
0
dead code introduced
Semantic Changes
51 symbols
~
tests/test_cmd_content_grep_hardening.py
.py
3 symbols added, 3 symbols removed, 5 symbols modified
← Older
Oldest on task/json-path-consistency
All commits
Newer →
Latest on task/json-path-consistency
0 comments
To add a comment, use the Muse CLI:
muse hub commit comment sha256:5d08a394a0ba78a4d517e40052ea84a2c57e82da0fbb3c73f59cc21ba1497def --body "your comment"
No comments yet. Be the first to start the discussion.