Skip to content

@flash-gordon flash-gordon released this Apr 23, 2019 · 70 commits to master since this release

1.0.0 2019-04-23


  • [BREAKING] Behavior of built-in constructor types was changed to be more strict. They will always raise an error on failed coercion (flash-gordon)

    # 0.15.0
    # => "foo"
    # 1.0.0
    # => Dry::Types::CoercionError: invalid value for Integer(): "foo"

    To handle coercion errors Type#call now yields a block:

    Types::Params::Integer.('foo') { :invalid } # => :invalid

    This makes work with coercions more straightforward and way faster.

  • [BREAKING] Safe types were renamed to Lax, this name better serves their purpose. The previous name is available but prints a warning (flash-gordon)

  • [BREAKING] Metadata is now pushed down to the decorated type. It is not likely you will notice a difference but this a breaking change that enables some use cases in rom related to the usage of default types in relations (flash-gordon)

  • Nominal types are now completely unconstrained. This fixes some inconsistencies when using them with constraints. Nominal#try will always return a successful result, for the previous behavior use Nominal#try_coerce or switch to strict types with passing a block to #call (flash-gordon)

Performance improvements

  • During the work on this release, a lot of performance improvements were made. dry-types 1.0 combined with dry-logic 1.0 are multiple times faster than dry-types 0.15 and dry-logic 0.5 for common cases including constraints checking and coercion (flash-gordon)


  • API for custom constructor types was enhanced. If you pass your own callable to .constructor it can have a block in its signature. If a block is passed, you must call it on failed coercion, otherwise raise a type coercion error (flash-gordon)
    proc do |input, &block|
      if input.is_a? String
        Integer(input, 10)
    rescue ArgumentError, TypeError => error
      if block
          backtrace: error.backtrace
    This makes the exception handling your job so that dry-types won't have to catch and re-wrap all possible errors (this is not safe, generally speaking).
  • Types now can be converted to procs thus you can pass them as blocks (flash-gordon)
    %w(1 2 3).map(&Types::Coercible::Integer)
    # => [1, 2, 3]

Compare v0.15.0...v1.0.0

Assets 2
You can’t perform that action at this time.