afaik validate-object-form-view also runs the view validators (which work across multiple fields) and the result of this validation step passes down into update-object-view-from-request.
is view-validation not enough for you? perhaps I misunderstood your question? On Mon, Jan 24, 2011 at 8:06 AM, Scott L. Burson <[email protected]> wrote: > On Jan 23, 6:13 pm, "Scott L. Burson" <[email protected]> wrote: > > I've encountered what seems to me to be a bug in the DATAFORM-SUBMIT- > > ACTION for QUICKFORM. It does CALL-NEXT-METHOD first, then calls its > > SATISFIES function (if provided). This means that the data object is > > written to the store before being validated, which doesn't make sense > > to me. What do you think? > > Actually, the real problem is that UPDATE-OBJECT-VIEW-FROM-REQUEST > provides no opportunity to validate the object between the point where > it is deserialized and the point where it is persisted. There is > field-wise validation done by VALIDATE-OBJECT-FORM-VIEW, but this > operates on a field/value alist, and happens before the object's slots > are filled with the values. Seems like UPDATE-... needs to accept the > SATISFIES function and call it at the right point. I'll submit a > patch, but first, am I missing anything here? > > -- Scott > > -- > You received this message because you are subscribed to the Google Groups > "weblocks" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<weblocks%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/weblocks?hl=en. > > -- You received this message because you are subscribed to the Google Groups "weblocks" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/weblocks?hl=en.
