A list of errors can be transformed into a nested map with errors. This is how it works in dry-validation. Eventually, different error representations will be a built-in feature.
Yes the DSL could be translated into a more verbose syntax where you’d do essentially the same thing that you do when using Ecto changesets. I’m not sure if I’d be interested in maintaining such functionality but it may turn out that this would Just Work OOTB. We’ll see how it goes 
Phoenix and Ecto integrations will be done as part of the package, at least in the beginning. If they grow a lot, I may extract them into ecto-drops and phoenix-drops.
Eventually, I’ll just document and compare Drops validation with other solutions, especially Ecto since it’s the most popular one.
