I think you could apply the same idea - use a regular translation between Java class and registered name and then always refer to the registered name.
There are probably multiple approaches to modeling inheritance, so hard to recommend something without knowing more. In general, attributes coming from super classes can be modeled using the parent attribute name. And I would recommend looking into multi-spec <http://clojure.github.io/clojure/branch-master/clojure.spec-api.html#clojure.spec/multi-spec> for doing validation of a number of "types" that could be flowing into the same location by leveraging a multimethod that conditionally provides the spec to use. On Monday, May 23, 2016 at 3:09:46 PM UTC-5, Andrey Grin wrote: > > Thanks, Alex. I've taken random example from plumatic.schema wiki to > quickly illustrate the question. In my actual use case I dynamically > generate schemas based on hundreds of model Java classes (beans) with > mutual references so I need recursion (and also some way to model > inheritance, that was is achieved with "conditional" in plumatic). Will try > to implement the same with spec. > > -- 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.
