MetaLad commands define parameter constraints in the same way that datalad core does. The newly introduced parameter validation in datalad-next provides a more powerful re-implementation of this, though. https://github.com/datalad/datalad-metalad/pull/357#issuecomment-1450290921 sketches what would be needed for a single command.
The hackathon and a call earlier today brought a few issues to light where parameter validation could have caught errors or problems early on, so I think metalad would benefit a lot from adopting it. However, it would bring a dependency to datalad-next, which would be new. What do you think, @christian-monch and @mih?
MetaLad commands define parameter constraints in the same way that datalad core does. The newly introduced parameter validation in
datalad-next
provides a more powerful re-implementation of this, though. https://github.com/datalad/datalad-metalad/pull/357#issuecomment-1450290921 sketches what would be needed for a single command.The hackathon and a call earlier today brought a few issues to light where parameter validation could have caught errors or problems early on, so I think metalad would benefit a lot from adopting it. However, it would bring a dependency to datalad-next, which would be new. What do you think, @christian-monch and @mih?