single quotes for controller generated routes #13705
Conversation
|
You'll need to rebase from master, it says it can't be merged. Also can you please add a changelog entry, then squash your commits? Thanks. |
|
Is there a convention to use of single vs double quotes that Rails tries to follow? I heard some say it's pretty much just easier to always use double quotes unless there is a specific need to not interpolate ruby or multibyte values, just to avoid all the hassle/diffs between the styles. |
|
@carlosantoniodasilva did rebase, squash and added the changelog entry. |
Write routes in route.rb with single quotes
get 'welcome/index'
instead of
get "welcome/index"
|
@egilburg yes, in general in the project we prefer to use single quotes unless double quotes are needed. It is a stylistic preference, single quotes are more specific, they signal to the reader right away the string has nothing fancy. As many stylistic conventions this is just a preference, I know people who always use double quotes. That's fine. |
Single quotes for controller generated routes. This is more consistent with all other Rails generated code.
Write routes in route.rb with single quotes
instead of