dry-validation

This release is mostly about upgrading to dry-core 1.0 and dry-configurable 1.0. One of the outcomes is dropping dependency on dry-container (because it was moved to dry-core). If you happen to use dry-container, please switch to Dry::Core::Container.

Changed

• Upgraded to the latest versions of dry-{core,configurable,logic,types} (@flash-gordon + @solnic)

Compare v1.9.0...v1.10.0

Fixed

• Duplicated keys mishandling in rule evaluation (issue #676 fixed via #711) (@mereghost)

Changed

• Use Zeitwerk for auto-loading (via #715) (@solnic)

Compare v1.8.1...v1.9.0

Fixed

• Raise an InvalidKeyErrors on substring of valid keys (issue #705 fixed via #706) (@MatElGran)
• Using rule(:arr).each { .. } doesn't crash when :arr turns out to be nil (issue #708 fixed via #709) (@bautrey37)

Compare v1.8.0...v1.8.1

Added

• New rule helper base_rule_error? which checks if there's any base error set (via #690) (@wuarmin)

Changed

• Dependency on dry-schema was bumped to 1.9.1 (@solnic)

Compare v1.7.0...v1.8.0

Changed

• [internal] Upgraded to new setting API provided in dry-configurable 0.13.0 (@timriley in #686 and 3f8f7d8)
• Bumped dry-schema dependency to 1.8.0 (in part, to ensure dry-configurable 0.13.0 is available) (@timriley)

Compare v1.6.0...v1.7.0

Added

• You can now pass a key name or path to rule_error? predicate (issue #658 closed via #673) (@moofkit)
• You can now pass initial context object to Contract#call (issue #674 via #675) (@pyromaniac)

Fixed

• Checking key? within a rule no longer crashes when value is nil or an empty string (issue #670 fixed via #672) (@alexxty7)

Compare v1.5.6...v1.6.0

Fixed

• Dependency on dry-schema was bumped to >= 1.5.1. This time for real (@solnic)

Compare v1.5.5...v1.5.6

Fixed

• Dependency on dry-schema was bumped to >= 1.5.2 (see #666 for more info) (@artofhuman)

Compare v1.5.4...master

Added

• You can now pass any key or a path to the rule's key? helper (see #664 for more info) (@alassek)

Fixed

• Full messages work correctly with rule failures now (issue #661 fixed via #662) (@stind)
• Providing a custom message template for array errors works correctly (issue #663 fixed via #665) (@tadeusz-niemiec)

Compare v1.5.3...v1.5.4

Added

• You can now access current value's index via rule(:foo).each do |index:| (issue #606 done via #657) (@mrbongiolo)

Fixed

• Using .each(:foo) works as expected when there are errors related to other keys (issue #659 fixed via #660) (@solnic)

Changed

• Result#error? is now a public API and it takes into consideration both schema and rule errors (issue #655 fixed via #656) (@PragTob)

Compare v1.5.2...v1.5.3

Fixed

• key? predicate in rules no longer crashes when the rule path points to a non-existent array value (issue #653 fixed via #654) (@solnic)
  Compare v1.5.1...v1.5.2

Fixed

• dry-monads no longer required for the :hints extension (@schokomarie)
• Using full: true option works as expected with custom rule messages (issue #618 fixed via #651) (@sirfilip)
• Using locale: ... option works as expected with hints (issue #589 fixed via #652) (@sirfilip)

Compare v1.5.0...v1.5.1

Added

• schema_error? rule helper (@waiting-for-dev)
• rule_error? rule helper (@waiting-for-dev)

Changed

• dry-schema dependency was bumped to ~> 1.5 (@solnic)
• [internal] KeyMap patches have been removed since dry-schema now provides required functionality (@solnic)

Compare v1.4.2...v1.5.0

Added

• Pattern matching on result values (@flash-gordon)

Fixed

• List tokens are correctly interpolated as a comma-separated list in rule messages (see #611) (@waiting-for-dev)
• Warnings about delegated keywords (@flash-gordon)

Compare v1.4.0...v1.4.1

Added

• Support for multi-schema inheritance (@ianwhite)

Fixed

• Keyword warnings reported by Ruby 2.7 (@flash-gordon)
• Fixed an issue where MessageSet would be marked as empty too early (@ianwhite)
• Messages are correctly generated when there are errors for both an array and one or more of its elements (see #599) (@Bugagazavr)

Changed

• A meaningful exception is raised when failure options are not valid (@MatElGran)
• [internal] improved performance in Contract.ensure_valid_keys (@grzegorz-jakubiak)
• [internal] fixed keyword warnings on MRI 2.7.0 (@flash-gordon)

Compare v1.3.1...v1.4.0

Added

• Support for setting an external schema (that can be extended too) (fixed #574) (@solnic)

Fixed

• Using a hash spec to define rule keys with more than one value is properly handled by rule guard now (fixed #576) (@solnic)

Changed

• values within rules uses Hash#fetch_values internally now, which improves performance (@esparta)

Compare v1.2.1...v1.3.0

Fixed

• Defining an abstract contract class that has no schema no longer crashes (issue #565) (@solnic)
• Fixed an issue where Rule#each would crash when the value is not an array (issue #567) (@solnic)
• Fixed an issue where guarding a rule would crash when keys are missing in the input (issue #569) (@solnic)
• Added missing "pathname" require (issue #570) (@solnic)

Compare v1.2.0...v1.2.1

Added

• New extension :predicates_as_macros (@waiting-for-dev)

Fixed

• Guarding rules for nested keys works correctly (issue #560) (@solnic)

Changed

• dry-schema dependency was bumped to >= 1.3.1 (@solnic)

Compare v1.1.1...v1.2.0

Fixed

• Rule#each works with array values from nested hashes (@mustardnoise)

Compare v1.1.0...v1.1.1

Added

• key? method available within rules, that can be used to check if there's a value under the rule's default key (refs #540) (@solnic)
• value supports hash-based path specifications now (refs #547) (@solnic)
• value can read multiple values when the key points to them, ie in case of rule(geo: [:lat, :lon]) it would return an array with lat and lon (@solnic)

Fixed

• Passing multiple macro names to validate or each works correctly (fixed #538 #541) (@jandudulski)

Compare v1.0.0...v1.1.0