So, you would give all those end-user-created specs a unique namespace prefix which identified them as part of your application. As Alex indicated, spec is predicated on the use of appropriately qualified names, so that they have global meaning.
Sean Corfield -- (970) FOR-SEAN -- (904) 302-SEAN An Architect's View -- http://corfield.org/ "If you're not annoying somebody, you're not really alive." -- Margaret Atwood On 6/12/17, 12:34 PM, "Mark" <clojure@googlegroups.com on behalf of markaddle...@gmail.com> wrote: 'm thinking of exposing the spec machinery to my app's end users who would build specs (probably using a graphical tool) to facilitate building data pipelines. It seems that the global registry assumes a particular lifecycle for specs which is probably perfect for developer-centric use cases. I believe I'll want a different lifecycle for specs written by end users. On Monday, June 12, 2017 at 12:19:04 PM UTC-7, Sean Corfield wrote: Can you explain why you think this is the case Mark? We use spec heavily in production (and have been doing so for months) so I’m not following your logic here I’m afraid… Sean Corfield -- (970) FOR-SEAN -- (904) 302-SEAN An Architect's View -- http://corfield.org/ "If you're not annoying somebody, you're not really alive." -- Margaret Atwood On 6/12/17, 10:37 AM, "Mark" <clo...@googlegroups.com on behalf of markad...@gmail.com> wrote: I'm a bit surprised by this. It seems that the use of the global registry limits spec to development use cases. Is that intentional? Maybe I'm worried over nothing On Saturday, June 10, 2017 at 11:04:17 AM UTC-7, Alex Miller wrote: We don't have any plans at the moment to support anything but the global registry. -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clo...@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+u...@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+u...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- 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. -- 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.
