Hi, I can understand the argument about different top-level namespaces, but...
Swagger2 depends on Mojo::JSON, Mojo::JSON::Pointer, Mojo::URL and Mojo::Util. I don't want to depend on other modules, just to avoid Mojo:: modules. Even so...I don't _think_ I would mind pull-requests to make it work with Mojo:: modules and/or other CPAN modules. Swagger2 can be used with other frameworks as well. Just use the Swagger2 module and skip the plugin. Mojolicious need to be installed though, because of the reasons i mentioned above. On Wednesday, December 10, 2014 10:38:49 AM UTC+1, Helmut Wollmersdorfer wrote: > > > > Am Dienstag, 9. Dezember 2014 16:02:11 UTC+1 schrieb Jan Henning Thorsen: >> >> >> Any feedback/ideas are very much appreciated. >> > > May I suggest that you unbundle it into two distributions > > - Swagger2 (without dependency on Mojolicious) > - Mojolicious::Plugin::Swagger2 > > The reasons: > > - the different top-level namespace > - minimal dependencies > - Swagger2 could be useful for other frameworks too > > Looking into the code I now saw that Swagger2 uses Mojo::Base & Co, which > I understand as convenient (I also did this for some CPAN modules, but > removed it before first release), but which IMHO isn't necessary. > > > -- You received this message because you are subscribed to the Google Groups "Mojolicious" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/mojolicious. For more options, visit https://groups.google.com/d/optout.
