You can dynamically install defmethods at runtime too so you could catch this problem when it falls into the default, generate the schema, register it, then re-invoke. Theoretically.
On Monday, May 23, 2016 at 4:20:38 PM UTC-5, Andrey Grin wrote: > > Thank you. Yes, it seems that for recursion I can use the same approach. > As for inheritance currently I just include all parent attributes in every > child schema. As for spec definition multi-spec, as I understand it, > requires "defmethod" for every class which is probably a problem for my > case since all inheritance hierarchies are also determined at run-time. I > will need to find some approach that is both dynamic and supports precise > error messages in case validation fails. > -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
