ony3000 / prettier-plugin-brace-style Goto Github PK

Dependency information

    "prettier": "^3.0.3",
    "prettier-plugin-brace-style": "^0.3.0",

Steps to reproduce

Just npm install

The current behavior

npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: [email protected]
npm WARN Found: [email protected]
npm WARN node_modules/prettier
npm WARN   dev prettier@"^3.0.3" from the root project
npm WARN   2 more (prettier-plugin-brace-style, @prettier/sync)
npm WARN
npm WARN Could not resolve dependency:
npm WARN peer prettier@"~2.8.4" from [email protected]
npm WARN node_modules/prettier-plugin-brace-style/node_modules/prettier-plugin-merge
npm WARN   optional prettier-plugin-merge@"~0.2.0" from [email protected]
npm WARN   node_modules/prettier-plugin-brace-style
npm WARN
npm WARN Conflicting peer dependency: [email protected]
npm WARN node_modules/prettier
npm WARN   peer prettier@"~2.8.4" from [email protected]
npm WARN   node_modules/prettier-plugin-brace-style/node_modules/prettier-plugin-merge
npm WARN     optional prettier-plugin-merge@"~0.2.0" from [email protected]
npm WARN     node_modules/prettier-plugin-brace-style

The expected behavior

No conflicts. This creates issues in some of my CI.

Dependency information

package.json

"dependencies": {
        "react": "^18.2.0",
        "react-dom": "^18.2.0"
    },
    "devDependencies": {
        "@figma/plugin-typings": "^1.76.0",
        "@prettier/sync": "^0.5.1",
        "@types/react": "^18.2.43",
        "@types/react-dom": "^18.2.17",
        "@typescript-eslint/eslint-plugin": "^6.14.0",
        "@typescript-eslint/parser": "^6.14.0",
        "@vitejs/plugin-react": "^4.2.1",
        "eslint": "^8.55.0",
        "eslint-plugin-react-hooks": "^4.6.0",
        "eslint-plugin-react-refresh": "^0.4.5",
        "prettier": "^3.2.5",
        "prettier-plugin-brace-style": "^0.5.0",
        "prop-types": "^15.8.1",
        "typescript": "^5.2.2",
        "vite": "^5.0.8",
        "vite-plugin-singlefile": "^0.13.5"
    }

.prettierrc

{
    "semi": true,
    "trailingComma": "none",
    "singleQuote": true,
    "tabWidth": 4,
    "printWidth": 100,
    "plugins": ["prettier-plugin-brace-style"],
    "braceStyle": "stroustrup"
}

Steps to reproduce

1. Create an empty function.
2. Make sure prettier is enabled to format on save file.
3. Save.

The current behavior

I have an empty code block like the following:

registerCallbacks() {}

When I save my file, it changes it to the following:

}
egisterCallbacks() {}

If I uninstall the plugin, the bug doesn't happen anymore. Is it conflicting with something else in VS code?

The expected behavior

No change to the code block on save.

Dependency information

VSCode 1.85.1
prettier 3.1.1
prettier-plugin-brace-style 0.5.0

Steps to reproduce

Select a block to format and use editor.action.formatSelection in VSCode.

The current behavior

VSCode has this cool feature called Format selection (editor.action.formatSelection) which allows me to only format my own blocks of a file without having to change it completely. The only reason for me to use this plugin would be to use prettier as formatter for this feature. Otherwise I would just use a relative feature in eslint and use it as formatter, because eslint doesn't have an api for Format selection and with your plugin so does prettier.

The expected behavior

Prettier has some kind of api for format selection which should be supported by the plugin.

Dependency information

For reference: https://tailwindcss.com/blog/automatic-class-sorting-with-prettier

The official prettier-plugin-tailwindcss will nicely sort your tailwind classes into an opinionated order. I would love to be able to use this classnames plugin, but unfortunately when I add it to my tailwind config it breaks the sorting that the official plugin provides.

Steps to reproduce

Add these plugins to your .prettierrc.json: (order doesn't matter)
"plugins": [
"prettier-plugin-tailwindcss",
"prettier-plugin-classnames"
]

The current behavior

Class sorting breaks while line wrapping still works

The expected behavior

Both class sorting and line wrapping work in harmony

Refs: prettier-plugin-merge#18

Dependency information

• [email protected]
• [email protected]

Steps to reproduce

Put one of these snippets in any JavaScript file and try to format it.

• round brackets

  function foo(/* args here */) {
    statement;
  }

• curly brackets

  if (condition) {
    // statement
  }

• square brackets

  const foo = [
    // elements
  ];

The current behavior

get an error Comment "..." was not printed.

The expected behavior

no errors.

Is your feature request related to a problem? Please describe

Could this be also applied to array of objects, like the below?

  await func(
    {
      a: '',
      b: '',
    },
    {
      a: '',
      b: '',
    }
  );

Describe the solution you'd like

In 1tbs, it should look like

  await func({
    a: '',
    b: '',
  }, {
    a: '',
    b: '',
  });

and like so in allman

  await func({
    a: '',
    b: '',
  }, 
  {
    a: '',
    b: '',
  });

Describe alternatives you've considered

Additional context

• testing-prettier-v2 branch
• testing-prettier-v3 branch

support for option "allowSingleLine"

This rule has an object option for an exception:
"allowSingleLine": true (default false) allows the opening and closing braces for a block to be on the same line

Nevermind error was on my account. had conflicting plugins.

Refs: prettier-plugin-classnames#17