On Wed, Apr 27, 2011 at 12:36:06PM -0700, Tim Shaffer wrote:
> The way I see it - if you were to create a folder on your computer
> to store recipies, what would you call it? Recipe or recipes?
I'd create a directory, and call it Recipes.
> I'd call it recipes since it holds more than one recipe. Then under
> there, you'd have each of your recipes as a file/folder. RESTful
> routes are designed to emulate that.
If that's how I was storing my recipes, that would make some sense.
But, I'm storing them in a database, so I have a little more
flexibility in how they're presented. If you were talking about a
beef brisket recipe, would you call it a beef brisket recipe, or a
beef brisket recipes? In that context, which of:
/Recipes/Beef-Brisket
/Recipe/Beef-Brisket
seems more natural?
> And is the case sensitivity that big of a deal?
If I give in to the all plural routes convention, the case sensitivity
issue isn't a big deal at all. Using my CamelCase preferences is as
simple as:
scope :path_names => { :new => "New", :edit => "Edit" } do
resources :movies, :path => "Movies"
end
--
Kevin
http://www.RawFedDogs.net
http://www.WacoAgilityGroup.org
Bruceville, TX
What's the definition of a legacy system? One that works!
Errare humanum est, ignoscere caninum.
--
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Talk" 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/rubyonrails-talk?hl=en.
