-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Scaffold Generation Unneccessary? #2
Comments
I completely agree. Maybe we could use Rails 3 way of doing this - a subapp? |
subapp seems like good idea, especially if that was how Rails3 intends for it to be used but then do we risk losing <= 2.3.5 support? seems like many repos (rspec and some other big ones included) are coming to same fork in road, whether to maintain 2 repos one that supports rails 2 the other rails 3. or one that supports both. Maybe this needs to be a separate discussion point tho. |
Differences between Rails 2 and 3 are too big to keep compatibility without having ugly code. I prefer moving forward, what you say? :) |
Yea I agree. We can keep the old stable branch up for people who want to use it. Call the new release B-Fu 2 and only support rails 3. People can grab the old stable branch from <= 2.3.5. If there is real request for it we can always merge things we know are supported into the old branch. |
Do the Jobs views & controllers, other scaffolding provided with b-fu really need to be generated? I don't see anything in them where templates are needed. We could just add a UI path and add it to the necessary load paths. Developers have to add to their routes.rb anyway. See http://github.com/jrwest/rcumber for an example.
The text was updated successfully, but these errors were encountered: