I'm using Rails 3.2, and have started with a scaffolding and built out from it, but have realized I need to rename the entire scaffold (Model, View, Controller, db:migrate, etc). Is there a built in way to do this, or should I just do it manually?
I don't think there's anything rails provides to rename the name of models/controllers/views/tests etc. once they are created - whether as a part of a scaffold, or not.
You will have to change it manually.
If it is a brand new app that you have just started on, it might be easier to just delete the whole directory/drop the database, and start over again.
If not, you will have to go through the files created/modified by the scaffold generation, and modify them manually.
Make sure you either drop_and_recreate the relevant table, or add a migration to rename the table. See How do you write a migration to rename an ActiveRecord model and its table in Rails? for some relevant advice.
I think there's no out of the box method to rename files generated by scaffold.What you have to do is create a new scaffold and copy your codes from the old to the new.Copy contents from factories, model, controller and their respective spec file to the new scaffold. Then remove the old scaffold with the command
rspec d scaffold <Model Name>
and you have to create a new migration to drop that old table from the database. Then run your migrations.
Related
I created controller, model and view using scaffold
rails generate scaffold Customer name:string
And then I did commit and then pushed everything in github and server. This was about a month ago. Now I need to undo the scaffold. I know I can do this by
rails destroy scaffold Customer
And this will undo the scaffold. My question is, this command rails destroy scaffold Customer do not generate any migration files. Then how destroying scaffold will have effect in server. How it will remove the files and models from server? Or do I have to do something else to undo the scaffold in server?
All that scaffold generate does is generate files from templates, and modifies your config/routes.rb file. The delete option deletes the files created. You can use the --pretend option to see what effect the change will have without running that command. So try:
rails destroy scaffold Customer --pretend
To see what will be changed by that action. Personally as the code has already gone into production, I'd probably do --pretend to generate the list of files that need to be removed and then delete each one manually after a quick review to check that doing so had no adverse effect.
When you update git the removed files will be marked as such in git, and pushing the change to the server via git will remove those files.
But, there are a couple of things to be careful of:
Migrations: do not delete the migration after it has been pushed to production and implemented there. Instead create a new migration that will drop the customers table. That way you will not mess up the migration sequence, and you will not be left with an unused table.
Routes: Check your config/routes.rb afterwards as I doubt the destroy scaffold will correctly reconfigure that.
Say I did rails g scaffold Review artist:string song:string genre:string and created a review object with those fields...would it later be possible to easily add another field like rating:int via a rails command, or would I need to manually edit all the files to include another data field for the form? I know it's possible to just delete the first scaffold and rebuild with the extra field, but I was just wondering if there was an easier way.
Thanks
The scaffold just generates minimalist model, view and controller code along with (usually) a database migration.
If you haven't made any serious changes to any of that code, it may be easier to rerun the scaffold generator. If you haven't run the database migrations, or you haven't committed them, you can add your attributes in the existing migration code and follow up with corresponding changes in the view.
If you've committed the code and someone is already depending on the existing model, you'll want to generate a database change migration to preserve a graceful upgrade/downgrade path.
The scaffold isn't magic, it's just a quick and dirty way of generating code that you can edit.
I'm very new to RoR and building my first application. I used rails generate scaffold and created a table in database. Of course I did it wrong, wanted to make changes to the table, did it by rewriting the generated migration file. I think rake db:migrate works fine, because it's updating my schema, but there are no changes visible on the site. The view of the table didn't change, although the mechanism is different, I can't add anything now because it can't find the proper columns after I changed them. I have no idea how to fix it without rewriting the view files myself. Is it possible, I think I'm missing something?
You can undo/destroy scaffold by rails destroy scaffold scaffold_name and then re-generate scaffold with the columns you added on migration file. FYI, editing migration files is not a good practice.
You have two options, either you destroy the scaffolding that you've created with rails destroy scaffold ModelName or you change the views by hand. When you run rake db:migrate it won't do anything in the views.
Is there an easy way to rename a controller and model in my app and all the instances in the corresponding code?
I'm using textmate, would this be as simple as using the replace function and replacing the word Post with Report?
You need to change the name of the Controller and the associated Model, Views, Helpers, Tests & Routes directories, file names, class names & the names in the class definitions.
I found two ways to do this but before you try anything I recommend you back-up your app, preferably with a Software Version Control system like Git & Github.com.
Your first option is to do it manually & there is a good explanation on how to do this here: How to rename rails controller and model in a project
Another way is to destroy your controller & model, and then generate a new one, this will remove all the files which were generated the first time round & replace them with new ones. Michael Hartl explains this solution well in his online guide to Ruby on Rails here: http://ruby.railstutorial.org/chapters/static-pages#sidebar-undoing_things
This is the solution I followed when I needed to make this change to my app, I needed to replace a MVC scaffold I generated called board with a new one called product.
1. First
I made a back-up of the work I did in the layout of the board view, app/views/boards/index.html.erb
2. Then
I ran the below rails commands in the terminal window.
$ rake db:rollback
$ rails destroy scaffold board name:string description:text image:string price:decimal
$ rails generate scaffold product product_type:string name:string description:text image:string price:decimal
$ rake db:migrate
3. Finally
I copied my backed-up boards/index.html.erb file into the newly generated app/views/products/index.html.erb & did a find & replace in my text editor on this file to replace board with product.
I think the second option is much more reliable & quicker but it’s important to make this change early on in your project before you make too many manual changes to the code. It would be better to just take a little more time planning your MVC names & database tables properly before you start your project.
You can also use rails_refactor gem to rename controller, model, etc
for more info check https://github.com/jcrisp/rails_refactor
To rename controller and model use this gem https://github.com/jcrisp/rails_refactor
If you are using textmate, use 'command-shift-f" to look for a string throughout your entire project.
Yes and no. You can rename it that way, but you'll also need to rename the files as well or Rails won't know where to look for the files corresponding to the new Report model/controller/etc.
Is there any way to re-generate views from newly updated model?
Unless you've made a lot of changes to the scaffold, it's probably easier just to overwrite the current scaffold:
./script/generate -f scaffold Model
I had the same need, I just backed up some changes and did a destroy/generate, Take care, destroy deletes Everything related to the Model :
rails destroy scaffold Model -f
before I generate again.
rails generate scaffold Model
The scaffold is not intended to create the interface, only to make a starting point for further development. I'm not sure it's even possible (without a lot of unnecessary work) to redo a scaffold, it's much quicker to manually edit the view and controller anyway.