Comments for rails's rails  

thanks :-)

I think you just need to change "generators/named_base" to "rails/generators/named_base". We namespaced everything in railties to /rails.

Hey @josevalim,

For 'dependency hell', I mean the 'require' statement I need to put in file when I tried to write a generator in lib/generator folder (like you). I tried your generators in third_rails but they don't work:

@@@ [WARNING] Could not load generator at "/tmp/lala/lib/generators/datamapper/model/model_generator.rb". Error: no such file to load -- generators/named_base [WARNING] Could not load generator at "/tmp/lala/lib/generators/rspec/model/model_generator.rb". Error: no such file to load -- generators/named_base Could not find generator rspec:model.
@@@

All old style generators won't work after the refactor on rails generator recently (?). I can't find an easy way to write new generator in lib/generators. Any idea?

This causes breakage: http://intertwingly.net/projects/AWDwR3/checkdepot.html

@janx, when you talk about dependency hell, you mean the dependencies declared in bundler?

I just posted a pastie explaining how to have your Rails 3 app working from edge without having to install gems or bundling twice:

http://pastie.org/684600

And if you want rspec generators, I created some in this branch:

http://github.com/josevalim/third_rails

However the rails used in vendor as a submodule is outdated. At least you can reuse lib/generators without problems.

I wrote a rspec built-in generator for rails3 yesterday (in my fork). I tried to write it as a plugin generator (like in lib/generators) but gave up finally due to the dependency hell :(

Is there any public api for plugin generator now?

No. Just that Rails 3 provides proper hooks to rpsec, so no more need for hacks and/or code duplication.

Is this means that Rails 3 will integrate rspec as build-in? like Merb?

Go qrush!

ftw!

gemcutter++

Congrats @qrush!

gah, sorry for the double post. /me fails at github

In ruby 1.8.6 and prior, date.rb has a bug wherein fractional seconds above 59 result in an invalid date. Try a "2005-02-27T23:50:59.275038".to_datetime and you'll see what I mean. Should we hack this to ignore fractional seconds above 59 when on broken ruby versions? It's kind of annoying when a method only works 59 times out of 60.

http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-core/23501

In ruby 1.8.6 and prior, date.rb has a bug wherein fractional seconds above 59 result in an invalid date. Try a "2005-02-27T23:50:59.275038".to_datetime and you'll see what I mean. Should we hack this to ignore fractional seconds above 59 when on broken ruby versions? It's kind of annoying when a method only works 59 times out of 60.

http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-core/23501

Thanks for that!

Not sure why this appeared in the events feed for rails/rails (I assume it was so that the branch could be deleted) but it had me worried for a while. No more commits ripping out the guts of important modules with messages like this one, please!

Broke down and created a plugin to do it. Manages seeds like models and allows rake db:seed to run individual model seeds, not just a batch.

http://github.com/markwfoster/seeded-generation

I think this changeset cause this error:
vendor/plugins/rack-mount/lib/rack/mount/route.rb:34:in `initialize': app must be a valid rack application and respond to call (ArgumentError)

from vendor/plugins/rack-mount/lib/rack/mount/generation/route.rb:9:in `initialize'
from vendor/plugins/rack-mount/lib/rack/mount/recognition/route.rb:9:in `initialize'
from vendor/plugins/rack-mount/lib/rack/mount/mixover.rb:25:in `new'
from vendor/plugins/rack-mount/lib/rack/mount/route_set.rb:46:in `add_route'
from vendor/plugins/rack-mount/lib/rack/mount/generation/route_set.rb:17:in `add_route'
from vendor/plugins/rack-mount/lib/rack/mount/recognition/route_set.rb:19:in `add_route'
from vendor/rails/actionpack/lib/action_dispatch/routing/route_set.rb:290:in `add_route'
from vendor/rails/actionpack/lib/action_dispatch/routing/deprecated_mapper.rb:147:in `connect'
from vendor/rails/actionpack/lib/action_dispatch/routing/deprecated_mapper.rb:213:in `named_route'
from vendor/rails/activesupport/lib/active_support/option_merger.rb:22:in `method_missing'
from vendor/rails/actionpack/lib/action_dispatch/routing/deprecated_mapper.rb:849:in `map_resource_routes'
from vendor/rails/actionpack/lib/action_dispatch/routing/deprecated_mapper.rb:801:in `map_default_collection_actions'
from vendor/rails/actionpack/lib/action_dispatch/routing/deprecated_mapper.rb:731:in `block in map_resource'
from vendor/rails/activesupport/lib/active_support/core_ext/object/with_options.rb:22:in `with_options'
from vendor/rails/actionpack/lib/action_dispatch/routing/deprecated_mapper.rb:723:in `map_resource'
from vendor/rails/actionpack/lib/action_dispatch/routing/deprecated_mapper.rb:642:in `block in resources'
from vendor/rails/actionpack/lib/action_dispatch/routing/deprecated_mapper.rb:642:in `each'
from vendor/rails/actionpack/lib/action_dispatch/routing/deprecated_mapper.rb:642:in `resources'
from config/routes.rb:2:in `block in <top (required)>'
from vendor/rails/actionpack/lib/action_dispatch/routing/route_set.rb:208:in `instance_exec'
from vendor/rails/actionpack/lib/action_dispatch/routing/route_s

I've already used your version of rack-mount. Is there anything missed?

Nevermind, I found it!
http://github.com/rails/arel/commit/35acdc90ec31d386c49b29a5db9c867db137e6ea