Include `Types::Params::String` about dry-types HOT 8 CLOSED

@adamransom should this be a coercible string?

from dry-types.

Well, a string is a string I guess 😄 but I see the Params namespace as a place for all things you would usually expect to receive from HTTP parameters, String being one of them.

Though perhaps it is purely meant for coercion of things from params, in which case I suppose my work-around is what's intended?

But yeah, this issue is mainly just an ergonomics thing when using default: :params.

from dry-types.

@adamransom I think it should be added as Types::Params::String = Types::Nominal::String because param values are either string, array or hash and we don't want to accidentely coerce an array or a hash into a string. Does this make sense?

from dry-types.

Yeah, definitely agree with that, and that's what I use as a workaround for now.

from dry-types.

Though I suppose if we go down this route, we'd need to add ones for array and hash too, in order to be consistent with Params having everything we'd expect from HTTP params.

from dry-types.

@adamransom good point. This also should be documented so that people don't expect any type of coercion.

from dry-types.

Right, I guess the short description is:

Params contains every type you would expect to receive via HTTP params, coercing where it makes sense. Currently, everything is coerced except Params::String, Params::Array and Params::Hash.

Would we want to use Nominal or Strict as the types behind Params::String, Params::Array and Params::Hash though? The params type raise if they can't be coerced, so I'd imagine the expectation is to raise if the type isn't an array, for example.

from dry-types.

Using nominal type won't work, see #394 But I think strict types should work 🤔

from dry-types.