Resources not new and not dirty should be considered valid
Reported by Nathan | July 17th, 2009 @ 11:53 AM | in 0.10.0
Getting a resource and then calling #valid? will rerun all validations, even tho it can be assumed that if it got into the Datastore it is valid.
I suppose I could see a time where you might want to rerun validations (if validations were updated), but I think this is an edge case and should have it's own work around (a way to force validations) and is unrelated to this current issue.
See here for a quick fix: http://gist.github.com/149155
Comments and changes to this ticket
-
Dan Kubb (dkubb) July 22nd, 2009 @ 09:55 AM
- State changed from “new” to “unconfirmed”
While I generally feel that persisted objects should be assumed to be valid, once you pull it back out of the datastore I'm not sure if that should be the case. I often will make applications to identify invalid records after tightening constraints, and either fix invalid records automatically if I can, or flag them for human review.
What are the problems you are seeing caused by the current behavior?
-
Dan Kubb (dkubb) July 22nd, 2009 @ 03:46 PM
- State changed from “unconfirmed” to “confirmed”
-
Dan Kubb (dkubb) July 22nd, 2009 @ 03:59 PM
- Assigned user set to “Dan Kubb (dkubb)”
- State changed from “confirmed” to “accepted”
-
Dan Kubb (dkubb) August 15th, 2009 @ 11:42 AM
- State changed from “accepted” to “not-applicable”
Marking this as not-applicable due to non-response when asking for more information from original submitter.
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
Dan Kubb (dkubb)
Nathan