Since the refactor of the validation logic, it now includes error codes and ids for each of the validation errors.
It would be great to review the errors to work out which ones are reasonable to silence and then support silencing them.
The silencing them might be something like having a meta.yml or validations.yml file which lists the errors which can be ignored along with a reason for why.
Even better might be some condition under which they need to be fixed by (e.g: after a particular match or time), though that likely isn't needed initially.
What would be good is to have a CLI flag on the validate command which supports showing all the errors (i.e: ignoring the silencings).
As part of this it would be good to ensure that each validation error is unique and that we can't accidentally silence errors we're not expecting to.
Since the refactor of the validation logic, it now includes error codes and ids for each of the validation errors. It would be great to review the errors to work out which ones are reasonable to silence and then support silencing them.
The silencing them might be something like having a
meta.ymlorvalidations.ymlfile which lists the errors which can be ignored along with a reason for why. Even better might be some condition under which they need to be fixed by (e.g: after a particular match or time), though that likely isn't needed initially. What would be good is to have a CLI flag on the validate command which supports showing all the errors (i.e: ignoring the silencings).As part of this it would be good to ensure that each validation error is unique and that we can't accidentally silence errors we're not expecting to.