Chris Markiewicz
Chris Markiewicz
Interested in getting your hands dirty? https://github.com/bids-standard/bids-validator/blob/4e2978da655cdecad34b4ad45ebda58170702551/src/main.ts#L44-L46 https://jsr.io/@std/path/doc/~/dirname https://docs.deno.com/api/deno/~/Deno.mkdir / https://docs.deno.com/api/deno/~/Deno.mkdirSync
If we do want to adopt it, we are required to specify `OutputLocation`, which we could default to stdout with `-o/--output -`. I'm not sure what `AnalysisLevel` would correspond to,...
I think we do load every TSV, so this should be doable if it's not already.
@rwblair We might already do this?
I think we need to think through the logic of the check before we worry about where to implement. Here's a proposal that only cares about collisions within directories: ```Python...
Would either of these checks catch @mattcieslak's motivating use case?
We've thought about how to handle situations like that. I'm happy to have the validator make a warning (which could be raised to an error by flag), but I wonder...
Also, this seems related to https://github.com/bids-standard/bids-validator/issues/836, which will also poke its nose behind the previously forbidden curtain of `.bidsignore`.
So the logic would move from: ``` if not ignore(file): validate(file) ``` To: ``` valid = validate(file) ignored = ignore(file) if not valid and not ignored: error if valid and...
Preserving part of bids-standard/legacy-validator#1103 in this issue: > I would be happy to see a (configurable) flag to limit `.bidsignore`d files to some file count, total file size, or proportion...