Skip to content

Upgrading dry-types 0.15 to 1

Breaking0.15.0 → 1.9.1Breaking3Platform2Deprecated2New19Changed12Fixed25Other3

Full comparisonBack to dry-types
BreakingUpgrade verdict

3 breaking changes and 2 platform requirement changes.

In plain terms
  • The 'safe' types have a new name, 'Lax'. The old name still works but shows a warning.
  • Type metadata now lives on the decorated type rather than the wrapper, which may affect code relying on where metadata is stored.
  • When a value cannot be converted to the expected type, these types now raise an error instead of silently returning the original value.
  • This version no longer runs on Ruby versions older than 3.2.
Must act Top 5 of 7 that need code or config changes

Ruby requirement changed in 1.9.0: >= 2.3.0 → >= 3.2.

What you must change

Breaking3
Safe types are renamed to Lax; the old name still works but prints a warning.
Lax
1.0.0GitHub ReleaseSummarizedView source
Metadata is now pushed down to the decorated type, a breaking change enabling rom use cases with default types in relations.
1.0.0GitHub ReleaseSummarizedView source
Built-in constructor types now always raise an error on failed coercion instead of returning the input.
Types::Params::IntegerDry::Types::CoercionErrorType#call
1.0.0GitHub ReleaseSummarizedView source
Platform2
Requires Ruby 3.2 or later.
1.9.0GitHub ReleaseSummarizedView source
Sets the minimum Ruby version to 3.1.
1.8.0GitHub ReleaseSummarizedView source

Deprecations to plan for

Deprecated2
Deprecates inferring predicates from class names; an exception with instructions is raised if relied upon.
Dry::Types::PredicateInferrer::Compiler.infer_predicate_by_class_name
1.5.0GitHub ReleaseSummarizedView source
Deprecates using Dry::Types.[] with classes.
Dry::Types.[]
1.2.0GitHub ReleaseSummarizedView source