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
Modeling errors like the one in the gist can be easily overlooked, and probably a better failure state is needed. Not being an expert on rails nested attributes, I'm not sure what the desired behavior is.
I'm not sure what the Rails Way to handle this is. But it would certainly be helpful to get an error when trying to assign non-existent attributes in cases like this.
no-reply
pushed a commit
to no-reply/active_fedora
that referenced
this issue
Apr 11, 2014
Sending a bad argument to Rdf::Resource#attributes= previously failed
silently. This is a problem, since it makes modeling errors invisible to
nested attributes setters, leading to missing data. Other Rails nested
attributes seem to throw an ArgumentError. This PR mimics that behavior
and message.
Closessamvera#393.
Created RdfList#to_ary and a mechanism for building list nodes.
Travis build samvera#393 failed, but samvera#392 passed and that references the same commit.
This problem was raised by issue (1) in this gist: https://gist.github.com/escowles/9975373.
Modeling errors like the one in the gist can be easily overlooked, and probably a better failure state is needed. Not being an expert on rails nested attributes, I'm not sure what the desired behavior is.
@jcoyne, @escowles: I'm hoping you can chime in.
The text was updated successfully, but these errors were encountered: