Interesting this - url_for does most of this (and also the passing an array
to do the parent/child dependencies) but not edit (so I tended to append
'/edit'). That'll teach me not to read the documentation between releases.

Form_for also supports passing arrays too, if you didn't know.

F

On Sun, May 17, 2009 at 1:49 PM, doug livesey <[email protected]> wrote:

> Brilliant, that's well useful to know -- cheers!
>    Doug.
>
> 2009/5/17 Lee Hambley <[email protected]>
>
> Doug, Caius,
>> I've just been working on a problem similar to this with a friend, he
>> wasn't aware of the square-bracket syntax, eventually managed to find some
>> documentation on it, so I am posting it here in his stead.
>>
>>    -
>>    
>> http://apidock.com/rails/ActionController/PolymorphicRoutes/polymorphic_url
>>
>> - Lee
>>
>> 2009/4/29 doug livesey <[email protected]>
>>
>> Not sure entirely what happened, but stubbing to_param out on my mock
>>> models seemed to fix things.
>>> Gift horse, mouth, not looking -- I'll reply back shortly, when my lack
>>> of investigation bites me again! ;)
>>>
>>> 2009/4/29 Lee Hambley <[email protected]>
>>>
>>> Thanks Paul [?]
>>>>
>>>> 2009/4/29 Paul Horsfall <[email protected]>
>>>>
>>>>  Does anyone know if that magic syntax has a name, and/or some
>>>>>> documentation?
>>>>>>
>>>>>
>>>>> link_to, form_for and friends all lean on url_for, which in turn leans
>>>>> on polymorphic_url for this bit of magic. Not really sure about the name,
>>>>> although 'resource-oriented style' is mentioned in the docs a few times I
>>>>> think.
>>>>>
>>>>> Paul
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>
>>
>>
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"NWRUG" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/nwrug-members?hl=en
-~----------~----~----~----~------~----~------~--~---

<<inline: 330.gif>>

Reply via email to