prettier VS black

✅ Angular 13 ✅ Angular Material ✅ Unit Testing with Jest ✅ End-to-End Testing with [TestCafé](https://testcafe.io/ ✅ Internationalization with Transloco ✅ Auto documentation with Compodoc ✅ Analyse your project with webpack-bundle-analyzer ✅ Docker ✅ ESLint ✅ Prettier ✅ Commit Linting ✅ AuditJS Audit this application using Sonatype OSS Index ✅ Auto-generate a CHANGELOG with auto-changelog

It would be best if you didn't argue about code formatting. Use a tool like prettier and never speak about the topic again. I don't put any effort whatsoever into formatting my code anymore. When I save, and nothing happens, this is a sign that there is a syntax error somewhere.

✅ Angular 13 ✅ Ngx-admin ✅ NestJS 8 ✅ Next generation build system with Nx ✅ Unit Testing with Jest ✅ End-to-End Testing with Cypress ✅ ESLint ✅ Prettier

✅ Angular 13 ✅ Angular Material ✅ Unit Testing with Jest ✅ End-to-End Testing with TestCafé ✅ Internationalization with Transloco ✅ Auto documentation with Compodoc ✅ Analyse your project with webpack-bundle-analyzer ✅ Docker ✅ ESLint ✅ Prettier ✅ Commit Linting

Prettier - Opinionated code formatter

Formatting code manually is very time-consuming and error-prone. With Prettier, the de-facto standard code formatter of the JavaScript world, you can format your code automatically. You can even configure the Prettier VS Code extension to format the source code when you save it.

This is what I use in my projects: Prettier to format the code. Eslint (for react) and Stylelint (for styles). You can additionally use husky to run the above linters and formaters before committing the code, you can also run some tests automatically before every commit, although depending on the number of tests, this can take some time and can be a bit annoying. In GitHub/GitLab, we also have a set of actions on our pipeline to run all of these linters and tests every time we create a merge request or deploy some new code (CI/CD).

✅ Prettier

🛠 Code Formatter with Prettier

Instead of worrying about formatting code yourself, you could use a code formatter. You can have your IDE than automatically format your code for you via a command, or set it up to automatically format on save. One such auto formatted is black. You can install it using pip install black. You can setup your IDE (ie VSCode) to then run the formatter when you save your .py file.

black is a code formatting tool

https://github.com/psf/black/issues/538 https://github.com/psf/black/pull/2726

I believe this is the issue:

https://github.com/psf/black/issues/1143

Not entirely clear what the reasons are for adding the Black dependency to IPython....

By which above poster means, use a code formatter, like black

or a code formatter like black

black: Black is the uncompromising Python code formatter. By using it, you agree to cede control over minutiae of hand-formatting. In return, Black gives you speed, determinism, and freedom from pycodestyle nagging about formatting. You will save time and mental energy for more important matters.