We use the legacy validator, but the schema validator will sooner (!) or later replace the legacy validator.
The schema validator will also be more accurate in covering the BIDS specification and might raise errors where the currently used legacy validator remained silent.
We should prepare for a switch, and the potential fixes at mne-bids that this may involve ... or at least be aware of it.
I think the right way would be to add an additional CI run to our suite that uses the schema validator, and then to try and make these tests pass bit by bit.
Currently there are two BIDS validator "builds":
We use the legacy validator, but the schema validator will sooner (!) or later replace the legacy validator.
The schema validator will also be more accurate in covering the BIDS specification and might raise errors where the currently used legacy validator remained silent.
We should prepare for a switch, and the potential fixes at mne-bids that this may involve ... or at least be aware of it.