Semantic Diff

#9249 Report every file in rescript format, in order, with short argument errors

2 commits

93de21011f6024dbdf80a45031608b9c0f7d4fdd..pr-9249

eaae59810 · cknitt + Claude · Nov 06, 2026, 20:54 UTC

Report every file in rescript format, in order, with short argument errors

Why

One file with a syntax error stopped rescript format, leaving other files unformatted; --check listed files in completion order with absolute paths, duplicate arguments counted twice, and invalid arguments surfaced raw compiler errors (#9243).

modifiedBehavior rescript format

representation
Before
After
a syntax error in one file ↦ the run stops; some other files stay unformattedformat --check ↦ files in completion order, absolute in project modeformat --check src/F.res src/F.res ↦ The 2 files listed above need formattingformat src/Missing.res ↦ We've found a bug for you! … I/O error: …: No such file or directoryformat src ↦ Error formatting src: don't know what to do with srcformat --stdin with a syntax error ↦ /tmp/rescript-format-7546c4.res:1:8-2:0a syntax error in one file ↦ every other file is formatted; the errors are reported, then the run failsformat --check ↦ files sorted, relative to the current directoryformat --check src/F.res src/F.res ↦ The file listed above needs formattingformat src/Missing.res ↦ src/Missing.res: No such fileformat src ↦ src is a directory; give .res or .resi files, or no arguments to format the projectformat --stdin with a syntax error ↦ <stdin>:1:8-2:0
82407f838 · cknitt + Claude · Nov 06, 2026, 21:29 UTC

Compare the format listing with forward slashes on Windows

Windows prints the relative paths with backslashes, which the new format-continues-after-syntax-error check compared literally.