You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is very helpful for more deeply nested schemas where it isn't clear which class is having its type check violated. Without it, the stacktrace and message provide little guidance, especially if there are multiple objects with the same attribute name.
Something like:
raiseSchema::Attribute::TypeError, "#{val.inspect} of type #{val.class.name} cannot be assigned to attribute #{attribute_name.inspect} of type #{type.name} in #{self.name} (Strict: #{strict.inspect})
The text was updated successfully, but these errors were encountered:
This is very helpful for more deeply nested schemas where it isn't clear which class is having its type check violated. Without it, the stacktrace and message provide little guidance, especially if there are multiple objects with the same attribute name.
Something like:
The text was updated successfully, but these errors were encountered: