-
Notifications
You must be signed in to change notification settings - Fork 0
CLI: repeating --input only processes the last file #119
Copy link
Copy link
Closed
Labels
area: cliTouches CLI / executable / bin entry pointsTouches CLI / executable / bin entry pointspriority: mediumShould be addressed in the normal course of developmentShould be addressed in the normal course of developmentstatus: implementedBuilt and deployed, but not yet fully tested/verifiedBuilt and deployed, but not yet fully tested/verifiedtype: bugSomething is broken or not behaving as expectedSomething is broken or not behaving as expected
Description
Activity
Metadata
Metadata
Assignees
Labels
area: cliTouches CLI / executable / bin entry pointsTouches CLI / executable / bin entry pointspriority: mediumShould be addressed in the normal course of developmentShould be addressed in the normal course of developmentstatus: implementedBuilt and deployed, but not yet fully tested/verifiedBuilt and deployed, but not yet fully tested/verifiedtype: bugSomething is broken or not behaving as expectedSomething is broken or not behaving as expected
Problem
Passing
--inputmore than once processes only the last value, and nothing says the earlier ones were dropped.Reproduced on
@cldmv/fix-headers@2.1.3in a fresh git project with two header-less files:a.mjsis left untouched andscanned=1. The obvious way to stamp just the files a change touched quietly skips all but the last one, so a header can be missing from a commit with no warning.Fix
Make
--inputrepeatable and process the union of every value given, in any order, with duplicates dropped. Folders should work as well as single files. If repeating it is deliberately unsupported, reject repeated--inputwith a clear error instead of silently keeping the last one. Add a CLI test for two--inputfiles.