This project is archived and is in readonly mode.

Changeset [67ee6c38b9b112eabe37d5869c23210b9ebf453c] by Prem Sichanugrist

June 24th, 2010 @ 07:17 PM

Remove the --singeleton option from scaffold generator.

It turned out to be that scaffold for singeleton resource will always depend on another model, and it's not possible at the moment to make the application tests pass after generate the singeleton scafold. So, it would be better to remove it for now and probably provide another generator, such as singeleton_scaffold, in which also require the depended model name.

[#4863 state:resolved]

Signed-off-by: José Valim

Committed by Prem Sichanugrist

  • M railties/lib/rails/generators.rb
  • M railties/lib/rails/generators/erb/scaffold/scaffold_generator.rb
  • M railties/lib/rails/generators/rails/resource/resource_generator.rb
  • M railties/lib/rails/generators/rails/scaffold_controller/scaffold_controller_generator.rb
  • M railties/lib/rails/generators/rails/scaffold_controller/templates/controller.rb
  • M railties/lib/rails/generators/test_unit/scaffold/scaffold_generator.rb
  • M railties/lib/rails/generators/test_unit/scaffold/templates/functional_test.rb
  • M railties/test/generators/resource_generator_test.rb
  • M railties/test/generators/scaffold_controller_generator_test.rb

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile »

<h2 style="font-size: 14px">Tickets have moved to Github</h2>

The new ticket tracker is available at <a href=""></a>