Skip to content
This repository has been archived by the owner on Apr 17, 2020. It is now read-only.

chore(deps): update dependency eslint-config-prettier to v6 #19

Open
wants to merge 1 commit into
base: dev
Choose a base branch
from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Aug 18, 2019

This PR contains the following updates:

Package Type Update Change
eslint-config-prettier devDependencies major 3.3.0 -> 6.10.0

Release Notes

prettier/eslint-config-prettier

v6.10.0

Compare Source

  • Added: [@​typescript-eslint/comma-spacing]. Thanks to Thanks to Masafumi
    Koba (@​ybiquitous)!!

v6.9.0

Compare Source

v6.8.0

Compare Source

  • Added: [@​typescript-eslint/no-extra-semi]. Thanks to @​xcatliu!

v6.7.0

Compare Source

  • Added: [@​typescript-eslint/space-before-function-paren]. Thanks to Masafumi
    Koba (@​ybiquitous)!

v6.6.0

Compare Source

  • Added: New [eslint-plugin-vue] rules: [vue/dot-location] and
    [vue/keyword-spacing]. Thanks to @​xcatliu!

v6.5.0

Compare Source

  • Added: Support for [excluding deprecated rules]. Thanks to Alex Ilyaev
    (@​alexilyaev)!

v6.4.0

Compare Source

  • Added: [unicorn/no-nested-ternary]. Thanks to Yang Mingshan
    (@​yangmingshan)!

v6.3.0

Compare Source

  • Added: [@​typescript-eslint/brace-style]. Thanks to Masafumi Koba
    (@​ybiquitous)!

v6.2.0

Compare Source

  • Added: [@​typescript-eslint/quotes] (as a [special
    rule][@​typescript-eslint/quotes-special]). Thanks to Masafumi Koba
    (@​ybiquitous)!

v6.1.0

Compare Source

  • Added: [function-call-argument-newline] (new in ESLint 6.2.0). Thanks to
    Masafumi Koba (@​ybiquitous)!

v6.0.0

Compare Source

  • Changed: The CLI helper tool now considers [no-confusing-arrow] to conflict
    if you use the default value of its allowParens option. The default was
    changed to true in ESLint 6, which conflicts with Prettier.

    If the CLI helper tool gives you errors about this after upgrading, the
    solution is to change this:

    {
      "rules": {
        "no-confusing-arrow": ["error"]
      }
    }

    Into this:

    {
      "rules": {
        "no-confusing-arrow": ["error", { "allowParens": false }]
      }
    }

    The latter works in both ESLint 6 as well as in ESLint 5 and older.

  • Improved: eslint --print-config usage instructions. The CLI tool help
    text as well as the documentation has been updated to suggest commands that
    work in ESLint 6.0 as well as in ESLint 5 and older. (Instead of eslint --print-config ., use eslint --print-config path/to/main.js.)

v5.1.0

Compare Source

  • Added: [react/jsx-curly-newline]. Thanks to Masafumi Koba (@​ybiquitous)!

v5.0.0

Compare Source

  • Removed: [react/self-closing-comp]. This rule was added in v4.1.0 not
    because it conflicted with Prettier but because it was unnecessary when
    using Prettier. However, in v1.18.0 [Prettier stopped converting empty
    elements to self-closing elements][prettier-self-closing]. So the rule is
    not unnecessary anymore.

    If you use Prettier v1.17.1 or older you should be able to upgrade
    eslint-config-prettier to v5.0.0 without having to do anything else.

    If you use Prettier v1.18.0 or newer, you might get lint errors about for
    example changing <div></div> into <div />. You have two options:

    • Run eslint --fix if you prefer to enforce self-closing elements where
      possible. This should fix all the errors.
    • Add "react/self-closing-comp": "off" to your ESLint config if you use
      autofix from your editor and you face the same [issue as Prettier
      did][prettier-self-closing].
  • Changed: Node.js 6 is no longer officially supported, but v5.0.0 should
    still work with it.

v4.3.0

Compare Source

  • Added: New [eslint-plugin-vue] rules: [vue/arrow-spacing],
    [vue/block-spacing], [vue/brace-style] and [vue/comma-dangle].
  • Added: New [@​typescript-eslint/eslint-plugin] rules:
    [@​typescript-eslint/func-call-spacing] and [@​typescript-eslint/semi].

v4.2.0

Compare Source

  • Added: [@​typescript-eslint/no-extra-parens]. Thanks to Keiichiro Amemiya
    (@​Hoishin) and Jen Gorfine (@​jgorfine)!

v4.1.0

Compare Source

  • Added: [linebreak-style]. Use Prettier’s [end-of-line] option instead.
  • Added: [react/self-closing-comp]. Thanks to Gaurav Gupta (@​gaurav5430)!

v4.0.0

Compare Source

  • Breaking change: Support for [eslint-plugin-typescript] has been removed and
    replaced with support for its successor [@​typescript-eslint/eslint-plugin].
    Thanks to TANIGUCHI Masaya (@​ta2gch) and everyone else who helped with this!
  • Changed: [arrow-body-style] and [prefer-arrow-callback] are now marked as
    [special rules][arrow-special], since they might cause problems if using
    [eslint-plugin-prettier] and --fix. They are turned off by default, and the
    CLI helper tool will warn about them (but not error if you do enable them).
    This won’t break your linting checks, but do note that these rules will be
    disabled unless you explicitly enable them again, and that you might see new
    warnings when running the CLI helper tool.

v3.6.0

Compare Source

  • Added: Support for [eslint-plugin-babel]. Thanks to Matija Marohnić
    (@​silvenon)!

v3.5.0

Compare Source

  • Fixed: The eslint-plugin-vue change from 3.4.0 has been reverted. That change
    requires eslint-plugin-vue@5, while many use eslint-plugin-vue@4. In other
    words, it was an accidental breaking change. Also, after thinking about it
    some more, it makes sense to have a Prettier-specific list of rules, rather
    than using the vue/no-layout-rules list, since there can be layout rules
    that don’t conflict with but rather complement Prettier.
  • Added: New eslint-plugin-vue rules coming in the next version after 5.1.0.

v3.4.0

Compare Source

  • Added: Support for [eslint-plugin-typescript]. Thanks to Jed Fox (@​j-f1)!
  • Improved: The eslint-plugin-vue integration is now using the
    vue/no-layout-rules config behind the scenes, so it should automatically
    stay up-to-date when new eslint-plugin-vue versions are released. Thanks to
    Michał Sajnóg (@​michalsnik)!

Renovate configuration

📅 Schedule: "after 10pm every weekday,before 5am every weekday,every weekend" (UTC).

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

♻️ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 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 WhiteSource Renovate. View repository job log here.

@renovate renovate bot added Bot: Renovate dependencies upgrade from renovate Priority: Low Low priority Status: In Review Need to review a issue/pull-request Type: Dependency For make any change with dependency labels Aug 18, 2019
@renovate renovate bot requested a review from kamontat August 18, 2019 10:00
@renovate renovate bot force-pushed the renovate/eslint-config-prettier-6.x branch from c3161e2 to b5992e8 Compare September 5, 2019 04:44
@renovate renovate bot force-pushed the renovate/eslint-config-prettier-6.x branch from b5992e8 to 053eb95 Compare October 4, 2019 09:56
@renovate renovate bot force-pushed the renovate/eslint-config-prettier-6.x branch from 053eb95 to 4a20b22 Compare November 11, 2019 12:58
@renovate renovate bot force-pushed the renovate/eslint-config-prettier-6.x branch from 4a20b22 to 3e0a658 Compare November 21, 2019 14:19
@renovate renovate bot force-pushed the renovate/eslint-config-prettier-6.x branch from 3e0a658 to a3557ac Compare December 31, 2019 03:55
Signed-off-by: Renovate Bot <bot@renovateapp.com>
@renovate renovate bot force-pushed the renovate/eslint-config-prettier-6.x branch from a3557ac to 495d692 Compare February 8, 2020 22:56
# for free to subscribe to this conversation on GitHub. Already have an account? #.
Labels
Bot: Renovate dependencies upgrade from renovate Priority: Low Low priority Status: In Review Need to review a issue/pull-request Type: Dependency For make any change with dependency
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants