Open effigies opened 5 months ago
@nellh What would be a good format for dataset_description? Right now it's:
ignore-entry1
ignore-entry2
...
ignore-entryN
0001
file1
file2
...
fileN
We could do:
{
...
}
0000
ignore-entry1
ignore-entry2
...
ignore-entryN
0001
file1
file2
...
fileN
This would be kinda backwards compatible, as the 0001
will continue to separate ignore and file listing, and then we could look for 0000\n
in the ignore list. But I'm not sure if we care about backwards compatibility, and if there might be something better.
Attention: Patch coverage is 1.47059%
with 67 lines
in your changes are missing coverage. Please review.
Project coverage is 83.89%. Comparing base (
bd08602
) to head (087ccb4
).:exclamation: Current head 087ccb4 differs from pull request most recent head ec42201. Consider uploading reports for the commit ec42201 to get more accurate results
Files | Patch % | Lines |
---|---|---|
tools/schemacode/bidsschematools/__main__.py | 0.00% | 67 Missing :warning: |
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
This is a basic validator that accepts a
.bidsignore
list and a list of files. The use case is to quickly determine if a git push should be accepted by a server.Todo:
dataset_description.json
from stdin, and enable derivativesfnmatch
filtering