Camel-case js route function names about js-routes

[jtrim]

It looks like this would be extremely easy to add. Any interest?

[le0pard]

And why is that? js routes comfortable that they have the same name as the ruby :)

[jtrim]

To solve the problem of case mismatch. If the standard / accepted case in the JS community is lower camel case, simply because something originates from a ruby source doesn't necessarily mean that it should retain the ruby standard case. Put a different way, if there was some piece of code that originated from javascript and was used in ruby, would you be at all put off by having to use camel case in a ruby file?

[le0pard]

So when data come from Rails/Ruby API in JSON format, do you also convert each key in camel-case?

[jtrim]

I have never done this myself, but it's not for lack of wanting the feature. I just haven't taken the time to search for a library that does this or patch rails for allowing it. If rails provided this feature out of the box, I'd use it.

[bogdan]

I would say that I am pretty ok with option like :camelcase => true.

But this is more likely to bring problems than solve them: track some helper usage in code becomes harder.

Anyway @jtrim concerns sounds reasonable to me.

[jtrim]

@bogdan I tend to agree with your assertion on tracking helper usage in a library. However, a problem isn't any less of a problem simply because the solution is hard.

[bogdan]

@jtrim you can go ahead with a patch. Please also update a doc and add a test case.

[jtrim]

Sounds good, will do. Thanks guys!

[slash]

You can actually do both. As the holy-war of the case will never end.
I don't think it will generate any issues, except for the fact that there will be a bit more code.
And confusion when people will use both cases in the same source.

[ches]

@slash Don't generate both cases -- in addition to inviting people to deviate from whatever the project's convention is as you mentioned, it'd double the size of the routes JS file.

[le0pard]

I think we can also close this issue :)