-
-
Notifications
You must be signed in to change notification settings - Fork 3.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
coffeescript constructors should not call return #1940
Conversation
+1 Fixes coffeescript-1.5.0 compatibility for me. |
@chourobin can you please remove that list of gems? It's really polluting this PR. The workaround is to backport coffee-script-source to 1.4.0 in your Gemfile. @ronen don't sweat it :) |
Do we need a workaround by downgrading |
@gregbell - Do you have any idea why the return statements were in there in the first place? Appears that everything is working fine for me with the return statements commented out, but want to be a bit cautious on this one. |
@macfanatic I haven't looked through the commit history of AA's CoffeeScript files, but just in general it's very convoluted and IMO backwards. I wouldn't be surprised if someone used an automated tool to convert the codebase from JavaScript, or otherwise didn't very well understand CoffeeScript. |
coffeescript constructors should not call return, compatible with coffeescript 1.5
coffeescript release 1.5.0 forbids explicit return statements in constructors. When used with the latest coffeescript, these two files now get compilation errors.
But the return statements in these two files were simply returning @, which is superfluous anyway. Deleted them and all seems good.