- v1.15.0Latest
- v1.15.1-dev.0
- v1.14.15-dev.0
- v1.14.14
- v1.14.14-dev.0
- v1.14.13
- v1.14.12
- v1.14.11
- v1.14.12-dev.0
- v1.14.10
- v1.14.11-dev.0
- v1.14.10-dev.0
- v1.14.9
- v1.14.9-dev.0
- v1.14.8
- v1.14.8-dev.0
- v1.14.7
- v1.14.7-dev.0
- v1.14.6
- v1.14.6-dev.0
- v1.14.5
- v1.14.4
- v1.14.5-dev.0
- v1.14.4-dev.0
- v1.14.3
- v1.14.2
- v1.14.3-dev.0
- v1.14.2-dev.0
- v1.14.1
- v1.14.1-dev.0
- v1.14.0
- v1.13.2-dev.0
- v1.13.1
- v1.13.0
- v1.13.1-dev.0
- v1.12.1-dev.0
- v1.12.0
- deno-release-demo-9dd96f2a
Deno based bids-validator
Intro
This is a partial rewrite of the bids-validator JavaScript implementation designed to read the bids-specification schema to apply the majority of validation rules.
Deno is a JavaScript and TypeScript runtime that is used to run the schema based validator. Deno is simpler than Node.js and only requires one tool to use, the Deno executable itself. To install Deno, follow these install instructions for your platform.
At the root of the repository there are two directories, bids-validator
and bids-validator-web
. These are separate npm packages, the Deno validator lives within the bids-validator package within the src
directory.
Schema validator examples
Deno by default sandboxes applications like a web browser. To validate datasets located on your local system, you need to use the –allow-read flag to read local files. –allow-env is also required to allow for detection of OS specific features. These flags are included in the script line of the ./bids-validator-deno
script.
# Run from within the /bids-validator directory
cd bids-validator
# Run validator:
./bids-validator-deno path/to/dataset
By default only schema derived validation rules are run. The legacy validator can be run at the same time with --legacy
and this may improve coverage for issues not yet implemented in the schema variant.
./bids-validator-deno --legacy path/to/dataset
Schema validator test suite
# Run tests:
deno test --allow-env --allow-read --allow-write src/
This test suite includes running expected output from bids-examples and may throw some expected failures for bids-examples datasets where either the schema or validator are misaligned with the example dataset while under development.
Refreshing latest specification
If you are validating with the latest specification instead of a specific version, the validator will hold onto a cached version. You can request the newest version by adding the --reload
argument to obtain the newest specification definition.
deno run --reload=https://bids-specification.readthedocs.io/en/latest/schema.json src/main.ts
Modifying and building a new schema
To modify the schema a clone of bids-standard/bids-specification will need to be made. README and schema itself live here https://github.com/bids-standard/bids-specification/tree/master/src/schema.
After changes to the schema have been made to a local copy the dereferenced single json file used by the validator will need to be built. The bidsschematools
python package does this. It can be installed from pypi via pip or a local installation can be made. It lives in the specification repository here https://github.com/bids-standard/bids-specification/tree/master/tools/schemacode
The command to compile a dereferenced schema is bst -v export --output src/schema.json
(this assumes you are in the root of the bids-specification repo). Once compiled it can be passed to the validator via the -s
flag, ./bids-validator-deno -s <path to schema> <path to dataset>