Prem Sichanugrist 67ee6c38b9 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 <jose.valim@gmail.com>		2010-06-24 20:17:59 +02:00
..
erb	Remove the --singeleton option from scaffold generator.	2010-06-24 20:17:59 +02:00
rails	Remove the --singeleton option from scaffold generator.	2010-06-24 20:17:59 +02:00
test_unit	Remove the --singeleton option from scaffold generator.	2010-06-24 20:17:59 +02:00
actions.rb
active_model.rb
base.rb	Changed ruby /path/to/rails myapp --dev to ruby /path/to/rails new myapp --dev in the "Thor is not avalable" message. [#4915 state:resolved]	2010-06-21 11:10:25 +02:00
erb.rb
generated_attribute.rb	Rails::Generators::GeneratedAttribute: tests, cleanups and a bugfix [#4631 state:resolved]	2010-06-10 20:04:49 +02:00
migration.rb
named_base.rb	Patch for Namespace problem in Scaffold. [#4763 state:resolved]	2010-06-23 09:30:55 +02:00
resource_helpers.rb	Patch for Namespace problem in Scaffold. [#4763 state:resolved]	2010-06-23 09:30:55 +02:00
test_case.rb	Rails::Generators::GeneratedAttribute: tests, cleanups and a bugfix [#4631 state:resolved]	2010-06-10 20:04:49 +02:00
test_unit.rb