A second, unrelated issue,
prettier-plugin-svelteconsole-logs some AST thing before it throws, and my vim plugin w0rp/ale which is running Prettier, overwrites my code with this output. I can undo, but it's sort of scary. So I'm wondering, from the perspective of Prettier, is the fault with vim/ale, or should prettier-plugin-svelte not print?
why is prettier formatting both the implementations differently —
Input :point_down:
type O1 = {
A: number
}
type O2 = {A: number}
Output :point_down:
type O1 = {
A: number;
};
type O2 = { A: number };
It maintains initial newlines, does seem so opinionated in my opinion :D
Hi there, having a question regarding https://prettier.io/docs/en/integrating-with-linters.html#recommended-configuration - Do these instructions make the above "Disable formatting rules" and "Use ESLint to run Prettier" eslint configurations unnecessary?
welp, just got my answer from https://cloudfour.com/thinks/getting-started-with-the-prettier-plugin-for-eslint/#comment-5322 ;)
Not just a git thing; it's a Unix thing: https://stackoverflow.com/questions/729692/why-should-text-files-end-with-a-newline
it's not working for me? it worked like one time and then quit
These are the setting I have in the settings.json file
{
"prettier.requireConfig": true,
"editor.defaultFormatter": "esbenp.prettier-vscode",
"editor.fontSize": 16,
"editor.tabSize": 2,
"prettier.useEditorConfig": false,
"prettier.printWidth": 80,
"workbench.iconTheme": "material-icon-theme",
"editor.formatOnSave": true
}
{
"prettier.requireConfig": true,
"editor.defaultFormatter": "esbenp.prettier-vscode",
"editor.fontSize": 16,
"editor.tabSize": 2,
"prettier.useEditorConfig": false,
"prettier.printWidth": 80,
"workbench.iconTheme": "material-icon-theme",
"editor.formatOnSave": true
}
Hello. I'm new to prettier and I run to the problem with formatting my async / await functions. In eslint configuration I have this rule dissabled have rule space-before-function-paren but still prettier is formatting the code incorrectly.
Expected formating:
test('Refresh token', async() {
const response = await chakram.post(`/v2/sso/refresh`, {
refreshToken
})
Joi.assert(response.body, validators.responsePostRefresh)
})Given:
test('Refresh token', async () {
const response = await chakram.post(`/v2/sso/refresh`, {
refreshToken
})
Joi.assert(response.body, validators.responsePostRefresh)
})Can you help me to not have space between async and brackets. What Am I missing?
Can you make an example in the playground so I can better see the issue @opravil-jan? https://prettier.io/playground
People who use Dart are very bothered by the 2-space indent enforced by dartfmt which automatically formats Dart and would like the option to be able to configure how Dart indent spacing is formatted. Im wondering if the Prettier plugin will ever support Dart since its very similar to Javascript. Here is a thread on github discussing this issue: Dart-Code/Dart-Code#914
I recently started using prettier v2 and stumbled across this issue: https://prettier.io/docs/en/options.html#end-of-line
Maybe I'm just too dense but I've been working with Windows, Mac and Linux for years now, frequently on the same code bases and never had an issue with line endings. Except for the rare cases when people thought that it's a good idea to use forced line ending settings that clashed with git's
git on Windows by default installs with
Maybe I'm just too dense but I've been working with Windows, Mac and Linux for years now, frequently on the same code bases and never had an issue with line endings. Except for the rare cases when people thought that it's a good idea to use forced line ending settings that clashed with git's
autocrlf. Which is exactly what happened to me now.git on Windows by default installs with
autocrlf (unless this was changed recently too), so why oh why would you introduce conflicts with this only to protect from maybe 2% of Windows users who have their git settings wrong?
Thanks but that just again describes the 2% case I mentioned and ignores the fact that now, millions of Windows users have to change their git configs to avoid seeing prettier errors on everything that they just cloned. As well as their IDE configs, since obviously some of them default to CRLF on Windows for good reason.
In case other confused/frustrated Windows developers end up here - this is a more substantial explanation for the "why oh why" 😉 prettier/prettier#5320
Hi there. Is there a possibility for somebody to have a second look on prettier/eslint-plugin-prettier#94 ? I've been trying the whole day to fix that problem for me. No success :(
@tjayrush AFAIK, there isn't a paid version, however, donations are appreciated: https://opencollective.com/prettier
(BTW, I'm not a member of the team, just an active community member)
Hi, I am developing a prettier plug-in for SQL. And I am having difficulty understanding how comments are handled. I am reading the source of estree printer as an examplar. I suppose there should be codes that attach comments to ast nodes, also there should be codes that print leading and trailing comments attached to nodes. But I cannot find these said codes. Can you help me with an outline about how comments are handled?
Hey guys, does anybody know why prettier formats these two constructors differently on ts?
I have prettier in visual studio code installed but not the plugin in the plugin. I talk from (https://github.com/prettier/plugin-php)