You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ATM we already interface multiple validators in dandi-cli. There are use cases which might ask for disabling or enabling some. Eg.
in cases of partial uploads of BIDS datasets we might want to disable bids-validator-deno as it would not have access to full dataset and just rely on bidsschematools which I believe we do not report otherwise (we do use it to extract metadata though)
where currently it is like auto as we do not bother with bids-validator(s) if we do not see it being a bids dandiset. With all it would really enable all of them.
Also I now created configuration label to mark issues which would point to specific options people must be able to specify for their dandisets locally (or globally).
it is not to "force" any particular validator on a specific path, but rather to alter (shrink) list of available validators which are applied as applicable.
for now blocked as we better decide on how to address is more holistically with 1743 and others.
What are the potential values of the --validators option?
auto. This one is clear. Just let the CLI to make decision. It is the current setting
all. This is also clear. Just apply all possible validators.
bidsschematools,bids-validator-deno,zarr,... is bit unclear. I supposed for values that are not auto or all, we only apply the corresponding validators that are explicitly specified? I guess that will mean we support multiple --validators options.
This will mean that we need to handle situations with multiple --validators options such as --validators auto --validators bidsschematools
something like that, or just allow for a comma-separated list. If it is confusing, as use of auto or all and explicit list -- issue a warning or even raise an error, I do not care.
Activity
candleindark commentedon Nov 6, 2025
What are the potential values of the
--validatorsoption?auto. This one is clear. Just let the CLI to make decision. It is the current settingall. This is also clear. Just apply all possible validators.bidsschematools,bids-validator-deno,zarr,...is bit unclear. I supposed for values that are notautoorall, we only apply the corresponding validators that are explicitly specified? I guess that will mean we support multiple--validatorsoptions.--validatorsoptions such as--validators auto --validators bidsschematoolsyarikoptic commentedon Nov 12, 2025
something like that, or just allow for a comma-separated list. If it is confusing, as use of
autooralland explicit list -- issue a warning or even raise an error, I do not care.