I've found naming a resource "Test" to be problematic, which is kind
of a drag in an educational application.
On Aug 28, 7:06 pm, carr wrote:
> On Aug 28, 1:17 pm, Jarl Friis wrote:
>
>
>
>
>
> > Hi.
>
> > I can't be the only one in the world having the wonderful idea to have
> > a resource n
On Aug 28, 1:17 pm, Jarl Friis wrote:
> Hi.
>
> I can't be the only one in the world having the wonderful idea to have
> a resource named "image".
>
> I have a controller named images_controller
> I have a route named "image", and therefore a helper called
> image_path(id).
>
> But using image_pa
"subclasses" class method is not accessible on ActiveRecord::Base
class, but it is on other classes like ActionController::Base.
Knowing the subclasses of AR::Base is pretty useful for every day
usage. Currently, I have to resort to the "send hack" to access this
information (not considering scan
On Thu, Aug 27, 2009 at 2:50 PM, Luciano G.
Panaro wrote:
>
> On Aug 27, 2:18 pm, Trek Glowacki wrote:
>> I like the concept and think it should be expanded to other
>> associations. We already define certain attributes of associated
>> objects for selecting, the symmetry of having build/create d
Hi.
I can't be the only one in the world having the wonderful idea to have
a resource named "image".
I have a controller named images_controller
I have a route named "image", and therefore a helper called
image_path(id).
But using image_path in an action view erb file gives problems, there
ano
