Not sure if this helps you, but I'm treating all my engine plugins as
standalone rails applications.
What this means is each engine plugin is theoretically able to run as
a standalone application and can therefor be tested the same way as
any other rails application. I think the overhead is accepta
Hi,
just a question / issue I came across when calling to_yaml on an
object which defines an association and called a method on this
association before the to_yaml. E.g. assume the following classes:
class Partner < ActiveRecord::Base
has_many :users
end
class User < ActiveRecord::Base
def
ion.
>
> Seems like a legit bug. Could you please wrap this up in a patch and
> create a LH ticket.
>
> I think files w/o an extension (in a view path) should be renderable
> without a template handler. I don't think they should be erb
> processed.
>
> On Jan
Hi,
quick question about _pick_template and template_file_extension.
The template_file_extension is extracted in the method but not used
later to find a template. This leads to the case were a template isn't
found and Template.new(template_path, view_paths) is called which
triggers a performance
I created a ticket with simplified application:
http://dev.rubyonrails.org/ticket/10925
Daniel
On Jan 25, 3:18 pm, "Michael Koziarski" <[EMAIL PROTECTED]> wrote:
> On Jan 26, 2008 5:10 AM, Daniel Guettler <[EMAIL PROTECTED]> wrote:
>
>
>
> > I came acr
I came across this when switching from rails 1.2.6 to 2.0.2, there is
a change in the way routes are generated between these to version due
to the routing optimization in rails 2.0.2.
In version 1.2.6 it was possible to overwrite the default_url_options
method in ActionController::Base to define p
