Make sails.getRouteFor() usage error message a bit clearer

Author: rachaelshaw

Diff for: .eslintrc

@@ -19,8 +19,7 @@
   },
 
   "parserOptions": {
-    "ecmaVersion": 5
-    // ^^This can be changed to `8` if this package doesn't need to support <= Node v6.
+    "ecmaVersion": 8
   },
 
   "globals": {

Diff for: lib/app/get-route-for.js

@@ -42,7 +42,7 @@ module.exports = function getRouteFor(routeQuery){
   try {
     actionToLookup = sails.router.getActionIdentityForTarget(routeQuery);
   } catch (unusedErr) { // FUTURE: provide access to error details instead of swallowing
-    var invalidUsageErr = new Error('Usage error: `sails.getRouteFor()` expects a string route target (e.g. "DuckController.quack") or a dictionary with either a target property (e.g. `{target: "DuckController.quack"}`) or an action property (e.g. `{controller: "duck", action: "quack"}` or `{action: "duck/quack"}`).  But instead, it received a `'+typeof routeQuery+'`: '+util.inspect(routeQuery, {depth: null}) );
+    var invalidUsageErr = new Error(`Usage error: sails.getRouteFor() expects a string route target (e.g. "DuckController.quack") or a dictionary with either a "target" (e.g. {target: "DuckController.quack"}) or an "action" (e.g. {controller: "duck", action: "quack"} or {action: "duck/quack"}).  But instead, it received a ${typeof routeQuery}: ${util.inspect(routeQuery, {depth: null})}`);
     invalidUsageErr.code = 'E_USAGE';
     throw invalidUsageErr;
   }