Support for array items in rule paths

Repository metrics

Stars

1,421 stars (1,421 stars)

PR merge metrics

No merged PRs in 30d (No merged PRs in 30d)

Description

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)
        required(:email).filled(:string)
        required(:phone).filled(:string)
      end
    end
  end

  rule("contacts[].email").each do
    key.failure("email not valid") unless value.include?('@')
  end
end

c = PropsContract.new

c.(
  contacts: [
    { name: 'Jane', email: 'jane@doe.org', phone: '123' },
    { name: 'John', email: 'oops', phone: '123' }
  ]).errors.to_h.inspect
# {:email=>{1=>["email not valid"]}}

Contributor guide

Research direction

Examine how rule paths currently work in dry validation and how array indices should be represented in the path syntax. Look at the example `"contacts[].email"` and related tests. Investigate the schema evaluation loop to understand how to iterate over array items and apply rules per element.

Tech stack

ruby

Domain

backendapi

Issue type

Feature

DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.

3

Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.

1-3 hours

Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.

Active

ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.

Mostly clear

Prerequisites

Rubydry validation

Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.

50