@solnic gotcha, I think I'm good to go with I get back to my machine. Do you think a good use case for this would be to verify request parameters for a client library and then to coerce values from a response body?
Assuming the case of a Dry::Struct class that points to a different Dry::Struct class as a type for one of its attributes, the depended upon class would have to be required first. What is the preffered approach to managing such dependecies –or in the least an approach that anyone has come across that works well?
@stergiom I doubt this, many things get broken when it comes to circular dependencies, dry-struct is no exception. However, ruby is flexible enough for this since it allows reopening a class, thus, you can load attribute-less definitions first, then load the rest of them. In practice, this means you put require right after class MyStruct < Dry::Struct