fix: correct misleading FileNotFoundError message in example#1004
fix: correct misleading FileNotFoundError message in example#1004VaibhavUpreti merged 1 commit intoTracer-Cloud:mainfrom
Conversation
The condition checks os.path.exists() but the error message says 'empty file' — should say 'input file' to match the missing-file condition. Closes Tracer-Cloud#828
Greptile SummaryThis PR corrects a one-line documentation fix in Confidence Score: 5/5Safe to merge — documentation-only fix with no code or logic changes. The change is a single-word correction in an example snippet inside a markdown file. It introduces no runtime behaviour changes and correctly aligns the error message with the condition it describes. All findings are P2 or lower. No files require special attention. Important Files Changed
Sequence DiagramsequenceDiagram
participant Caller
participant use_case as use_case.py
participant OS as os.path
Caller->>use_case: extract_and_validate(input_path)
use_case->>OS: exists(input_path)
OS-->>use_case: False
use_case-->>Caller: raise FileNotFoundError("input file not present: {input_path}")
Reviews (1): Last reviewed commit: "fix: correct misleading FileNotFoundErro..." | Re-trigger Greptile |
|
Spotted that #1002 is fixing the same line in the same file for issue #828. Both fixes are correct. Wording-wise I lean toward #1002's "not found" since it matches the FileNotFoundError convention, but happy to defer. cc @davincios / @VaibhavUpreti for which to merge. |
Summary
Fixed the misleading
FileNotFoundErrormessage in the example code. Changed "empty file not present" to "input file not present" to correctly match theos.path.exists()condition being checked.Related
Closes #828