On Friday, July 19, 2013 1:47:37 PM UTC+1, James Coleman wrote:
Particularly given that relations are already themselves proxies that
> generally quack like arrays but lazily-load items. The `all` method is
> specifically there so that you can *break out* *of that proxy*.
>
As of Rails 4, Model
On 29 Aug 2009, at 19:36, Michael Koziarski
wrote:
> If someone wants to take a stab at this, I'm keen to take a look at
> a patch.
I'd quite like to take a shot at it, but I haven't contributed to the
core before -is there a policy/procedure document somewhere I can take
a look at firs
One of the approaches I saw used in an old attachment plugin - don't
remember which one - was to check this in an asset tag helper. The
helper in this case could ne patched to return an engine override if
one exists, which would allow the frontend to continue serving the
assets.
-Matt
On
On 29 Aug 2009, at 18:49, Adam Milligan wrote:
> I'm not sure this is a Rails problem. Most web apps have an 'images'
> directory under the public web root.
That's really kind of sidestepping the issue though. It's not just
resources called 'images' that this happens to, and there's absolutel
