prettier 1.2.2 → 1.4.0

data/src/nodes/commands.js

@@ -1,91 +0,0 @@
-const {
-  align,
-  concat,
-  group,
-  ifBreak,
-  indent,
-  join,
-  line,
-  softline
-} = require("../prettier");
-const { docLength, makeCall } = require("../utils");
-
-const hasDef = (node) =>
-  node.body[1].type === "args_add_block" &&
-  node.body[1].body[0].type === "args" &&
-  node.body[1].body[0].body[0] &&
-  ["def", "defs"].includes(node.body[1].body[0].body[0].type);
-
-// Very special handling case for rspec matchers. In general with rspec matchers
-// you expect to see something like:
-//
-//     expect(foo).to receive(:bar).with(
-//       'one',
-//       'two',
-//       'three',
-//       'four',
-//       'five'
-//     )
-//
-// In this case the arguments are aligned to the left side as opposed to being
-// aligned with the `receive` call.
-const skipArgsAlign = (path) =>
-  ["to", "not_to"].includes(path.getValue().body[2].body);
-
-// If there is a ternary argument to a command and it's going to get broken
-// into multiple lines, then we're going to have to use parentheses around the
-// command in order to make sure operator precedence doesn't get messed up.
-const hasTernaryArg = (path) =>
-  path.getValue().body[1].body[0].body.some((node) => node.type === "ifop");
-
-module.exports = {
-  command: (path, opts, print) => {
-    const command = path.call(print, "body", 0);
-    const joinedArgs = join(concat([",", line]), path.call(print, "body", 1));
-
-    const hasTernary = hasTernaryArg(path);
-    let breakArgs;
-
-    if (hasTernary) {
-      breakArgs = indent(concat([softline, joinedArgs]));
-    } else if (hasDef(path.getValue())) {
-      breakArgs = joinedArgs;
-    } else {
-      breakArgs = align(command.length + 1, joinedArgs);
-    }
-
-    return group(
-      ifBreak(
-        concat([
-          command,
-          hasTernary ? "(" : " ",
-          breakArgs,
-          hasTernary ? concat([softline, ")"]) : ""
-        ]),
-        concat([command, " ", joinedArgs])
-      )
-    );
-  },
-  command_call: (path, opts, print) => {
-    const parts = [
-      path.call(print, "body", 0),
-      makeCall(path, opts, print),
-      path.call(print, "body", 2)
-    ];
-
-    if (!path.getValue().body[3]) {
-      return concat(parts);
-    }
-
-    parts.push(" ");
-
-    const joinedArgs = join(concat([",", line]), path.call(print, "body", 3));
-    const breakArgs = skipArgsAlign(path)
-      ? joinedArgs
-      : align(docLength(concat(parts)), joinedArgs);
-
-    return group(
-      ifBreak(concat(parts.concat(breakArgs)), concat(parts.concat(joinedArgs)))
-    );
-  }
-};

data/src/nodes/hooks.js

@@ -1,44 +0,0 @@
-const { concat, group, indent, line } = require("../prettier");
-const { isEmptyStmts } = require("../utils");
-
-// The `BEGIN` and `END` keywords are used to hook into the Ruby process. Any
-// `BEGIN` blocks are executed right when the process starts up, and the `END`
-// blocks are executed right before exiting.
-//
-//     BEGIN {
-//       # content goes here
-//     }
-//
-//     END {
-//       # content goes here
-//     }
-//
-// Interesting side note, you don't use `do...end` blocks with these hooks. Both
-// nodes contain one child which is a `stmts` node.
-function printHook(name) {
-  return function printHookWithName(path, opts, print) {
-    const stmtsNode = path.getValue().body[1];
-    const printedStmts = path.call(print, "body", 1);
-
-    const parts = [
-      name,
-      " ",
-      path.call(print, "body", 0),
-      indent(concat([line, printedStmts])),
-      concat([line, "}"])
-    ];
-
-    // If there are no statements but there are comments, then we want to skip
-    // printing the newline so that we don't end up with multiple spaces.
-    if (isEmptyStmts(stmtsNode) && stmtsNode.comments) {
-      parts[1] = indent(printedStmts);
-    }
-
-    return group(concat(parts));
-  };
-}
-
-module.exports = {
-  BEGIN: printHook("BEGIN"),
-  END: printHook("END")
-};

data/src/parser.js

@@ -1,86 +0,0 @@
-const { spawnSync } = require("child_process");
-const path = require("path");
-
-// In order to properly parse ruby code, we need to tell the ruby process to
-// parse using UTF-8. Unfortunately, the way that you accomplish this looks
-// differently depending on your platform.
-const LANG = (() => {
-  const { env, platform } = process;
-  const envValue = env.LC_ALL || env.LC_CTYPE || env.LANG;
-
-  // If an env var is set for the locale that already includes UTF-8 in the
-  // name, then assume we can go with that.
-  if (envValue && envValue.includes("UTF-8")) {
-    return envValue;
-  }
-
-  // Otherwise, we're going to guess which encoding to use based on the system.
-  // This is probably not the best approach in the world, as you could be on
-  // linux and not have C.UTF-8, but in that case you're probably passing an env
-  // var for it. This object below represents all of the possible values of
-  // process.platform per:
-  // https://nodejs.org/api/process.html#process_process_platform
-  return {
-    aix: "C.UTF-8",
-    darwin: "en_US.UTF-8",
-    freebsd: "C.UTF-8",
-    linux: "C.UTF-8",
-    openbsd: "C.UTF-8",
-    sunos: "C.UTF-8",
-    win32: ".UTF-8"
-  }[platform];
-})();
-
-// This function is responsible for taking an input string of text and returning
-// to prettier a JavaScript object that is the equivalent AST that represents
-// the code stored in that string. We accomplish this by spawning a new Ruby
-// process of parser.rb and reading JSON off STDOUT.
-function parse(text, _parsers, _opts) {
-  const child = spawnSync(
-    "ruby",
-    ["--disable-gems", path.join(__dirname, "./parser.rb")],
-    {
-      env: Object.assign({}, process.env, { LANG }),
-      input: text,
-      maxBuffer: 10 * 1024 * 1024 // 10MB
-    }
-  );
-
-  const error = child.stderr.toString();
-  if (error) {
-    throw new Error(error);
-  }
-
-  const response = child.stdout.toString();
-  return JSON.parse(response);
-}
-
-const pragmaPattern = /#\s*@(prettier|format)/;
-
-// This function handles checking whether or not the source string has the
-// pragma for prettier. This is an optional workflow for incremental adoption.
-function hasPragma(text) {
-  return pragmaPattern.test(text);
-}
-
-// This function is critical for comments and cursor support, and is responsible
-// for returning the index of the character within the source string that is the
-// beginning of the given node.
-function locStart(node) {
-  return node.char_start;
-}
-
-// This function is critical for comments and cursor support, and is responsible
-// for returning the index of the character within the source string that is the
-// ending of the given node.
-function locEnd(node) {
-  return node.char_end;
-}
-
-module.exports = {
-  parse,
-  astFormat: "ruby",
-  hasPragma,
-  locStart,
-  locEnd
-};