I have a question about dry-struct
I want to use it to define a new value object however looks like I need to use the attribute DSL method to actually define attributes
what will happen if the Types module doesn't have the type that I want to wrap inside this new struct?
the type is an active record model
my intention is to use dry-struct to define value objects in my code base; I've been doing that with struct however I see the value on having some type checks for structs and probably in the future I will be able to compose smaller structs into bigger ones
any thoughts ?
@cored you can use
Types::Any.constrained(type: ARModel)
what does that do ? @flash-gordon
so the actual syntax would be attribute Types::Any.constrained(type: ARModel) ?
builds a type with a single type-check
oh I see
so I will be able to pass anything that conforms to an active record model interface?
I'm still deciding if dry-struct would be a good inclusion
the advantage that I see at this point is the deep freeze feature
re any model, yes is you do it like
Dry::Types['any'].constrained(type: ApplicationRecord), or you can specify a concrete class Dry::Types['any'].constrained(type: UserRecord), depends on your needs
the downside of the concrete type
is that I will create a dependency with the framework
something that I don't want directly I would like to depend on the protocol instead of the specific type definition
oh now that I see it
looks like I need to pass an actual type into the type: key
is that right @flash-gordon ?
yes, it'a just an
.is_a? check
gotcha
I'm getting an error
method missing is complaining about 'keys'