I agree. I added the "vars-on-top" -- it also encourages the use of "let" over "var" for block scoped variables. Good call.
I could go either way on the “one var per line” rule. But I have read a few decent arguments in favor of using it. --- ** [tickets:#8035] Finalize frontend eslint/jscs setup** **Status:** in-progress **Milestone:** unreleased **Labels:** sf-current sf-4 **Created:** Mon Dec 14, 2015 03:48 PM UTC by Heith Seewald **Last Updated:** Mon Jan 25, 2016 06:27 PM UTC **Owner:** Heith Seewald **Attachments:** - [.eslintrc](https://forge-allura.apache.org/p/allura/tickets/8035/attachment/.eslintrc) (416 Bytes; application/octet-stream) - [.jscsrc](https://forge-allura.apache.org/p/allura/tickets/8035/attachment/.jscsrc) (169 Bytes; application/octet-stream) Finalize and cleanup our eslint/jscsrc setup. This can be a working standard that evolves over time -- but we should get something in place now so that we can start collecting feedback. *(Dave has a few tweaked config files attached - they need more work though)* Then apply these styles to [#7919]. --- Sent from forge-allura.apache.org because [email protected] is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
