Skip to content
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

Update dependency prettier to v1.16.4 #853

Merged
merged 1 commit into from
Feb 8, 2019
Merged

Conversation

ghost
Copy link

@ghost ghost commented Dec 3, 2018

This PR contains the following updates:

Package Type Update Change References
prettier devDependencies minor 1.15.2 -> 1.16.4 homepage, source

Release Notes

prettier/prettier

v1.16.4

Compare Source

diff

  • 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

Compare Source

diff

  • 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

Compare Source

diff

  • 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)

    <!-- Input -->
    Prix·:·32·€
    
    <!-- Output (Prettier 1.16.1) -->
    Prix : 32 €
    
    <!-- Output (Prettier 1.16.2) -->
    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

Compare Source

diff

  • 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.

    <!-- Input -->
    _foo <InlineJSX /> bar_
    
    <!-- Output (Prettier 1.16.0) -->
    _foo
    
    <InlineJSX /> bar_
    
    <!-- Output (Prettier 1.16.1) -->
    _foo <InlineJSX /> bar_

v1.16.0

Compare Source

diff

🔗 Release Notes

v1.15.3

Compare Source

diff

  • 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)

Renovate configuration

📅 Schedule: "before 3am on Monday" in timezone Europe/Zurich.

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻️ Rebasing: Whenever PR becomes conflicted, or if you modify the PR title to begin with "rebase!".

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

@ghost ghost requested a review from rschlaefli as a code owner December 3, 2018 01:01
@ghost ghost added the dependencies label Dec 3, 2018
@ghost ghost assigned rschlaefli Dec 3, 2018
@ghost ghost changed the title Update dependency prettier to v1.15.3 Update dependency prettier to v1.16.0 Jan 20, 2019
@ghost ghost changed the title Update dependency prettier to v1.16.0 Update dependency prettier to v1.16.1 Jan 22, 2019
@ghost ghost changed the title Update dependency prettier to v1.16.1 Update dependency prettier to v1.16.2 Jan 30, 2019
@ghost ghost changed the title Update dependency prettier to v1.16.2 Update dependency prettier to v1.16.3 Jan 31, 2019
@ghost ghost changed the title Update dependency prettier to v1.16.3 Update dependency prettier to v1.16.4 Feb 3, 2019
@rschlaefli rschlaefli merged commit 6be1494 into master Feb 8, 2019
@rschlaefli rschlaefli deleted the renovate/prettier branch February 8, 2019 11:33
rschlaefli pushed a commit that referenced this pull request Aug 4, 2021
Bumps [mongoose](https://github.com/Automattic/mongoose) from 5.7.12 to 5.8.4.
- [Release notes](https://github.com/Automattic/mongoose/releases)
- [Changelog](https://github.com/Automattic/mongoose/blob/master/History.md)
- [Commits](Automattic/mongoose@5.7.12...5.8.4)

Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

1 participant