@Johann Pardanaud Hi! I am now using this library in the second project and here we have the requirement to attach metadata to constraint violations. E.g. I validate a list of items that can be in conflict with each other (something like a unique check on an attribute of the list items) and I need to have the conflicting items as metadata for the constraint violation.
The premium solution would be to supply the type of the Constraint Violation as a sealed class to akkurate, so that I can have a "normal" constraint violation with a path and a message, but also specialized types for "This thing here conflicts with this other thing".
Something like this would be the minimum vialable solution:
https://github.com/nesk/akkurate/pull/63
Any thoughts on that?