Skip to content

upload,validate: Add --validators option #1737

Open

Description

@yarikoptic

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)
  • ...

So I think we should add an option like

  • --validators auto,all,bidsschematools,bids-validator-deno,zarr,...

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).

edits:

  • note that such filtering on validators, relates to the Add filtering of issues by type/ID or by file location #1743
  • 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.

Activity

  1. candleindark commented on Nov 6, 2025

    @candleindark
    Member

    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
  2. yarikoptic commented on Nov 12, 2025

    @yarikoptic
    MemberAuthor

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

blockedBlocked by some needed development/fixcmd-uploadcmd-validateconfigurationpotentially pointing to configuration parameters to be defined etc

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions