Pick a better naming schema for association views
Reported by Yurii Rashkovskii | April 29th, 2008 @ 10:20 AM | in 0.0.3
Currently I just #to_json all options. But that's definitely weird name. I need a better idea.
Comments and changes to this ticket
-
Yurii Rashkovskii April 29th, 2008 @ 09:25 PM
- State changed from “new” to “resolved”
Here is an example of new naming schema — "http://coolapp.com#user_has_many_items"
-
Yurii Rashkovskii May 13th, 2008 @ 03:13 PM
(from [07d858a8aa8c90771089dfa21abe0f2ac6fbc4a7]) better naming schema for association views [#25 state:resolved]
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
StrokeDB is an embeddable distributed document database written in Ruby
Yurii Rashkovskii