plannotator annotate <file> returns File not found: <path> when given a non-markdown file that exists on disk. The path resolves correctly — the failure is actually a file-type filter.
Repro (Windows, Git Bash, Plannotator 0.19.17):
$ plannotator annotate notes/design.md
Resolved: C:\...\notes\design.md # works
$ plannotator annotate lib/util.cs
File not found: lib/util.cs # file exists
$ plannotator annotate C:\repo\lib\util.cs
File not found: ... # absolute path, still fails
Two requests:
-
Fix the error message — say "File type not supported (only .md/plan files accepted)" instead of "File not found". Current message wastes time debugging path/Windows/Git Bash issues that aren't there.
-
Feature request — annotate source code files. Many workflows benefit from inline annotation of code (e.g. .cs, .ts, .py) the same way as plans/specs. /plannotator-review exists for code review, but it's a different UX (diff review vs. inline line-by-line annotation). Having annotate accept any text file would unify the experience.
Environment:
- OS: Windows 11
- Shell: Git Bash (MSYS2)
- Plannotator: 0.19.17
plannotator annotate <file>returnsFile not found: <path>when given a non-markdown file that exists on disk. The path resolves correctly — the failure is actually a file-type filter.Repro (Windows, Git Bash, Plannotator 0.19.17):
Two requests:
Fix the error message — say "File type not supported (only .md/plan files accepted)" instead of "File not found". Current message wastes time debugging path/Windows/Git Bash issues that aren't there.
Feature request — annotate source code files. Many workflows benefit from inline annotation of code (e.g.
.cs,.ts,.py) the same way as plans/specs./plannotator-reviewexists for code review, but it's a different UX (diff review vs. inline line-by-line annotation). Havingannotateaccept any text file would unify the experience.Environment: