Open shadyvb opened 8 years ago
They key aim for validators is to provide some frameworking to allow developers to run custom checks on imported content, generally this should be entirely up to the developer to decide if/when/how to use validators on a migration.
We may need to extend validator capabilities to allow more flexibility on collection and display of validator output, but would keep in mind that a validator (in my opinion) is just a secondary use case for an iterator.
It would help if we have a list of use-cases that we need to cover with validators, so we can best judge if the current architecture is suitable or not, and how to work towards a better arch. if needed.
Current use-cases would include: