Search code, repositories, users, issues, pull requests...

TypeScript: only add trailing commas in tuples for --trailing-comma=all ([#6199] by @duailibe)

In Prettier 1.18 we added trailing commas in tuples when --trailing-comma=all, but it was also adding for --trailing-comma=es5.

[#6199]: #6199

@duailibe: https://github.com/duailibe

`v1.18.1`

TypeScript: Add trailing comma in tsx, only for arrow function (#6190 by @sosukesuzuki)

Prettier inserts a trailing comma to single type parameter for arrow functions in tsx, since v 1.18. But, this feature inserts a trailing comma to type parameter for besides arrow functions too (e.g, function , interface). This change fix it.

// Input
interface Interface1<T> {
  one: "one";
}
function function1<T>() {
  return "one";
}

// Output (Prettier 1.18.0)
interface Interface1<T,> {
  one: "one";
}
function function1<T,>() {
  return "one";
}

// Output (Prettier 1.18.1)
interface Interface1<T> {
  one: "one";
}
function function1<T>() {
  return "one";
}

Config: Match dotfiles in config overrides (#6194 by @duailibe)

When using overrides in the config file, Prettier was not matching dotfiles (files that start with .). This was fixed in 1.18.1

`v1.18.0`

`v1.17.1`

Range: Fix ranged formatting not using the correct line width (#6050 by @mathieulj)

// Input
function f() {
  if (true) {
    call("this line is 79 chars", "long", "it should", "stay as single line");
  }
}

// Output (Prettier 1.17.0 run with --range-start 30 --range-end 110)
function f() {
  if (true) {
    call(
      "this line is 79 chars",
      "long",
      "it should",
      "stay as single line"
    );
  }
}

// Output (Prettier 1.17.0 run without range)
function f() {
  if (true) {
    call("this line is 79 chars", "long", "it should", "stay as single line");
  }
}

// Output (Prettier 1.17.1 with and without range)
function f() {
  if (true) {
    call("this line is 79 chars", "long", "it should", "stay as single line");
  }
}

JavaScript: Fix closure compiler typecasts ([#5947] by @jridgewell)

If a closing parenthesis follows after a typecast in an inner expression, the typecast would wrap everything to the that following parenthesis.

// Input
test(/** @&#8203;type {!Array} */(arrOrString).length);
test(/** @&#8203;type {!Array} */((arrOrString)).length + 1);

// Output (Prettier 1.17.0)
test(/** @&#8203;type {!Array} */ (arrOrString.length));
test(/** @&#8203;type {!Array} */ (arrOrString.length + 1));

// Output (Prettier 1.17.1)
test(/** @&#8203;type {!Array} */ (arrOrString).length);
test(/** @&#8203;type {!Array} */ (arrOrString).length + 1);

JavaScript: respect parenthesis around optional chaining before await (#6087 by @evilebottnawi)

// Input
async function myFunction() {
  var x = (await foo.bar.blah)?.hi;
}

// Output (Prettier 1.17.0)
async function myFunction() {
  var x = await foo.bar.blah?.hi;
}

// Output (Prettier 1.17.1)
async function myFunction() {
  var x = (await foo.bar.blah)?.hi;
}

Handlebars: Fix {{else}}{{#if}} into {{else if}} merging (#6080 by @dcyriller)

// Input
{{#if a}}
  a
{{else}}
  {{#if c}}
    c
  {{/if}}
  e
{{/if}}

// Output (Prettier 1.17.0)
{{#if a}}
  a
{{else if c}}
  c
e
{{/if}}

// Output (Prettier 1.17.1)
Code Sample
{{#if a}}
  a
{{else}}
  {{#if c}}
    c
  {{/if}}
  e
{{/if}}

JavaScript: Improved multiline closure compiler typecast comment detection (#6070 by @yangsu)

Previously, multiline closure compiler typecast comments with lines that
start with * weren't flagged correctly and the subsequent parenthesis were
stripped. Prettier 1.17.1 fixes this issue.

// Input
const style =/**
 * @&#8203;type {{
 *   width: number,
 * }}
*/({
  width,
});

// Output (Prettier 1.17.0)
const style =/**
 * @&#8203;type {{
 *   width: number,
 * }}
*/ {
  width,
};

// Output (Prettier 1.17.1)
const style =/**
 * @&#8203;type {{
 *   width: number,
 * }}
*/({
  width,
});

`v1.17.0`

`v1.16.4`

API: Fix prettier.getSupportInfo() reporting babel parser for older versions of Prettier. (#5826 by @azz)

In version 1.16.0 of Prettier, the babylon parser was renamed to babel. Unfortunately this lead to a minor breaking change: prettier.getSupportInfo('1.15.0') would report that it supported babel, not babylon, which breaks text-editor integrations. This has now been fixed.

`v1.16.3`

TypeScript: Revert "Update typescript-estree to new package name" (#5818 by @ikatyang)

There's an internal change introduced in Prettier 1.16.2,
which updated typescript-estree to its new package name,
but unfortunately it broke the output
so we reverted it as a temporary workaround for now.

// Input
export default {
  load<K, T>(k: K, t: T) {
    return {k, t};
  }
}

// Output (Prettier 1.16.2)
export default {
  load(k: K, t: T) {
    return { k, t };
  }
};

// Output (Prettier 1.16.3)
export default {
  load<K, T>(k: K, t: T) {
    return { k, t };
  }
};

`v1.16.2`

CLI: Fix CI detection to avoid unwanted TTY behavior (#5804 by @kachkaev)

In Prettier 1.16.0 and 1.16.1, --list-different and --check logged every file in some CI environments, instead of just unformatted files.
This unwanted behavior is now fixed.
HTML: Do not format non-normal whitespace as normal whitespace (#5797 by @ikatyang)

Previously, only non-breaking whitespaces (U+00A0) are marked as non-normal whitespace,
which means other non-normal whitespaces such as non-breaking narrow whitespaces (U+202F)
could be formatted as normal whitespaces, which breaks the output. We now follow the spec to
exclude all non-ASCII whitespace from whitespace normalization.

(· represents a non-breaking narrow whitespace)
```

Prix·:·32·€


Prix : 32 €


Prix·:·32·€
```

JavaScript: Fix record type cast comment detection (#5793 by @yangsu)

Previously, type cast comments with record types were ignored and prettier
stripped the subsequent parens. Prettier 1.16.2 handles these cases correctly.

// Input
const v = /** @&#8203;type {{key: number}} */ (value);

// Output (Prettier 1.16.1)
const v = /** @&#8203;type {{key: number}} */ value;

// Output (Prettier 1.16.2)
const v = /** @&#8203;type {{key: number}} */ (value);

`v1.16.1`

JavaScript: Do not format functions with arguments as react hooks (#5778 by @SimenB)

The formatting added in Prettier 1.16 would format any function receiving an
arrow function and an array literal to match React Hook's documentation.
Prettier will now format this the same as before that change if the arrow
function receives any arguments.

// Input
["red", "white", "blue", "black", "hotpink", "rebeccapurple"].reduce(
  (allColors, color) => {
    return allColors.concat(color);
  },
  []
);

// Output (Prettier 1.16.0)
["red", "white", "blue", "black", "hotpink", "rebeccapurple"].reduce((
  allColors,
  color
) => {
  return allColors.concat(color);
}, []);

// Output (Prettier 1.16.1)
["red", "white", "blue", "black", "hotpink", "rebeccapurple"].reduce(
  (allColors, color) => {
    return allColors.concat(color);
  },
  []
);

JavaScript: Add necessary parentheses for decorators (#5785 by @ikatyang)

Parentheses for decorators with nested call expressions are optional for legacy decorators
but they're required for decorators in the current proposal.

// Input
class X {
  @&#8203;(computed().volatile())
  prop
}

// Output (Prettier 1.16.0)
class X {
  @&#8203;computed().volatile()
  prop
}

// Output (Prettier 1.16.1)
class X {
  @&#8203;(computed().volatile())
  prop
}

TypeScript: Stable parentheses for function type in the return type of arrow function (#5790 by @ikatyang)

There's a regression introduced in 1.16 that
parentheses for function type in the return type of arrow function were kept adding/removing.
Their parentheses are always printed now.

// Input
const foo = (): (() => void) => (): void => null;
const bar = (): () => void => (): void => null;

// First Output (Prettier 1.16.0)
const foo = (): () => void => (): void => null;
const bar = (): (() => void) => (): void => null;

// Second Output (Prettier 1.16.0)
const foo = (): (() => void) => (): void => null;
const bar = (): () => void => (): void => null;

// Output (Prettier 1.16.1)
const foo = (): (() => void) => (): void => null;
const bar = (): (() => void) => (): void => null;

MDX: Correctly recognize inline JSX (#5783 by @ikatyang)

Previously, some inline JSXs are wrongly recognized as block HTML/JSX,
which causes unexpected behaviors. This issue is now fixed.
```

_foo <InlineJSX /> bar_


_foo

<InlineJSX /> bar_


_foo <InlineJSX /> bar_
```

`v1.16.0`

`v1.15.3`

JavaScript: support htm (#5565)
JavaScript: support logical assignment operator (#5489)
JavaScript: do not add quotes for interpolation-only attributes in html templates (#5544)
JavaScript: add missing parenthesis for binary in optional member (#5543)
JavaScript: fix a parser regression (#5530)
JavaScript: improve union types with leading comments (#5575)
TypeScript: support BigInt (#5546, #5577)
TypeScript: inline method decorators should stay inlined (#5444)
TypeScript: do not change module into namespace and break/hug their body correctly (#5551)
TypeScript: do not add invalid semicolon for construct in interface with // prettier-ignore (#5469)
HTML: do not touch comments (#5525)
HTML: preserve bogus comments <! ... >/<? ... > (#5565)
HTML: support IE conditional start/end comment (#5470)
HTML: do not add extra indentation for js template in <script> (#5527)
HTML: leading spaces for the first interpolation in <textarea> are sensitive (#5468)
HTML: preserve content for element in <pre> correctly (#5473)
HTML: correct column for error code frame (#5553)
Angular: support interpolation in attributes (#5573)
Angular: do not print colon for then and else in *ngIf (#5542)
Angular/Vue: do not normalize tag/attribute names (#5526, #5549)
Vue: preserve custom block (#5458)
Vue: remove unnecessary semicolon and preserve necessary semicolon for single expression in event bindings (#5519)
Vue: group slot-scope correctly (#5563)
Markdown: do not trim content in inline-math (#5485)
Markdown: add more category to CJK regex (#5480)
SCSS: update parser for performance improvements (#5481)
YAML: preserve the first document head end marker --- (#5502)
API: resolve ignored field correctly in .getFileInfo() with absolute filePath (#5570)
API/CLI: fix a bug that caches for .js config files did not respect .clearConfigCache() (#5558)
API/CLI: ignore unset in .editorconfig (#5550)
CLI: report status code 0 for --list-different + --write (#5512)
Standalone: fix a regression for browser compatibility (#5560)

`v1.15.2`

CLI: allow flag overriding (#5390)
JavaScript: do not apply test call formatting to arrow function without body (#5366)
JavaScript: do not duplicate comments in styled-components (#5416)
JavaScript: do not indent comments behind variable declarations (#5434)
JavaScript: inline property decorator should stay inline (#5364, #5423)
JavaScript: treat createSelector as function composition (#5430)
Flow: do not move flow comment for function argument to its body (#5435)
Flow: force-break interface body to be consistent with TypeScript interface (#5432)
Flow/TypeScript: remove extra indentation for extends (#5432)
TypeScript: distinguish module and namespace correctly (#5432)
HTML: handle CRLF correctly (#5393)
HTML: handle <pre> with interpolation (#5400)
HTML: preserve content for <template> with unknown lang (#5388)
HTML: preserve incomplete IE conditional comments (#5429)
HTML: preserve unterminated IE conditional comments (#5424)
HTML: treat capital element as custom element (#5395)
Angular: add missing parens for pipe in ternary (#5397)
Angular: correctly print unary expression with operator + (#5405)
Angular: correctly handle parens (#5387)
Angular/Vue: whitespaces between interpolation and text are sensitive (#5396)
Vue: do not add invalid semicolon for v-on attribute value (#5418)
SCSS: do not crash on grid value (#5394)
Markdown: handle CRLF correctly (#5414)
Markdown: identify CJK correctly (#5402)
MDX: treat JSX code block same as in Markdown (#5391)

`v1.15.1`

Markdown: do not keep increasing backslashes for dollar sign (#5358)

`v1.15.0`