[rspec-users] [PLUGIN] rspec_resource_generator - RESTful scaffold generator with RSpec specifications

Pat Maddox pergesu at gmail.com
Sun Nov 5 08:31:50 EST 2006


On 11/5/06, aslak hellesoy <aslak.hellesoy at gmail.com> wrote:
> On 11/5/06, David Chelimsky <dchelimsky at gmail.com> wrote:
> > On 11/4/06, aslak hellesoy <aslak.hellesoy at gmail.com> wrote:
> > > On 11/4/06, Pat Maddox <pergesu at gmail.com> wrote:
> > > > On 11/4/06, aslak hellesoy <aslak.hellesoy at gmail.com> wrote:
> > > > > On 11/4/06, Pat Maddox <pergesu at gmail.com> wrote:
> > > > > > http://svn.flpr.org/public/plugins/rspec_resource_generator/
> > > > > >
> > > > > > Most code shamelessly jacked from the scaffold_resource plugin.  I
> > > > >
> > > > > The generators in Rails *will* evolve and copying/forking its code
> > > > > will inevitably result in a maintenance nightmare (or obsoletion).
> > > > >
> > > > > That's why the existing RSpec generators (rspec_model and
> > > > > rspec_controller) _reuse_ the templates from Rails instead of forking
> > > > > them. The only templates we wrote ourselves are the ones that generate
> > > > > the specs. Maintaining that is easy - it's *our* code.
> > > > >
> > > > > Would you consider refactoring your code according to this principle
> > > > > and delete all the duplicated (copied) code? In that case we'll
> > > > > include your contribution into RSpec on Rails.
> > > > >
> > > > > There is already an RFE for it here:
> > > > > http://rubyforge.org/tracker/index.php?func=detail&aid=6098&group_id=797&atid=9464
> > > >
> > > > All done.  The only template remaining is the controller_spec
> > > > template.  Everything else is pulled from the standard Rails
> > > > generators, and the rspec_model generator for the model spec.
> > > >
> > > > Anything else that should be done with that?
> > > >
> > >
> > > Not that I know of - sounds great! I'll take a look at it tonight.
> > >
> > > Thanks a lot!
> >
> > Agreed that this is great stuff.
> >
> > We're about to do a release that has changed some things about which
> > there seem to be some assumptions in the controller_spec template.
> >
> > What I'd propose is that we wait until after the release for this. We
> > can tweak it to fit the newer approaches and then add it to rspec for
> > the next release.
> >
>
> Agreed. Pat, is it ok for you if we steal your code and check it into
> RSpec's svn when time is ripe?
>
> You'll be credited here: http://rspec.rubyforge.org/team.html
>
> Aslak

I'm not sure...that DoWhatYouWantWithIt license is pretty stringent :)

Feel free to put it in whenever you think is good, and make whatever
changes you feel appropriate as David mentioned.

Pat


More information about the rspec-users mailing list