Skip to content

Commit 71800c8

Browse files
authored
formatting fixes
1 parent 9f211aa commit 71800c8

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

README.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -59,19 +59,19 @@ The basic configuration format is outlined below. All configuration is optional.
5959

6060
`ignoredFiles` takes a list of file paths or glob patterns you'd like to ignore. Lets say we want to ignore all files and sub-directory under `/derivatives/`.
6161

62-
{
63-
"ignoredFiles": ["/derivatives/**"]
64-
}
62+
{
63+
"ignoredFiles": ["/derivatives/**"]
64+
}
6565

6666
Note that adding two stars `**` in path makes validator recognize all files and sub-dir to be ignored.
6767

6868
`ignore`, `warn`, and `error` take lists of issue codes or issue keys and change the severity of those issues so they are either ignored or reported as warnings or errors. You can find a list of all available issues at [utils/issues/list](https://github.com/INCF/bids-validator/tree/master/utils/issues/list.js).
6969

7070
Some issues may be ignored by default, but can be elevated to warnings or errors. These provide a way to check for common things that are more specific than BIDS compatibility. An example is a check for the presence of a T1w modality. The following would raise an error if no T1W image was found in a dataset.
7171

72-
{
73-
"error": ["NO_T1W"]
74-
}
72+
{
73+
"error": ["NO_T1W"]
74+
}
7575

7676
In addition to issue codes and keys these lists can also contain objects with and "and" or "or" properties set to arrays of codes or keys. These allow some level of conditional logic when configuring issues. For example:
7777

0 commit comments

Comments
 (0)