Svyatoslav Kryukov

I have created this issue just for visibility, since personally, I use `Oj::Rails.mimic_JSON` to overcome this issue 😅

We should wait for maintainers, I'm just an outsider 😅

@solnic shouldn't the rule be without `.each`? ```ruby rule("contacts[].email") do key.failure("email not valid") unless value.include?('@') end rule("contacts[].emails").each do key.failure("email not valid") unless value.include?('@') end ```

@solnic I see your point, but how we will differentiate, should we iterate over `emails` or use `email` as a target item for the rule? Maybe we should introduce another...

@solnic I'll try to explain =) For example, we have a schema like this: ```ruby require 'dry-validation' class PropsContract < Dry::Validation::Contract json do required(:contacts).value(:array, min_size?: 1).each do hash do required(:name).filled(:string)...

I would propose to introduce the `root` keyword: ```ruby Dry::Schema.JSON do root.array(:integer) end ``` To implement this I would: - add a special `__root__` key to the schema - wrap...

> besides, the biggest problem I think is producing error messages, not the DSL part I think you can pass a special option to the `message_compiler` to skip the first...

@solnic @flash-gordon AFAIC `.type` does not affect anything except the coercion step, am I right? Is there any case when one should use `.type` instead of `.value` / `.filled`?

Hi, @peterberkenbosch thanks for the issue report! I've run `dip provision` on the mac with M1, and it works ok. The only thing, I've increased docker memory limits so that...

It can break someone with a modified PATH also https://github.com/evilmartians/lefthook/issues/178