* Followup work on setup github actions * Coverage report & split `prod_lint` * Add env * Remove coverage report on azure pipelines * Remove build step on lint * remove coverage report on prod_test * Use `ci-info` instead of `is-ci` * Always enable `ENABLE_TEST_RESULTS` and `AST_COMPARE` on CI * Standalone test and remove some env * coverage report * reduce matrix * standalone test * `ci-info` * Remove token * Disable `coverage` on azure pipelines * use master version of codecov-action * Link to master status * fix prod lint * Use boolean env * Remove locv report * Try lcov report * pin `codecov-action` version, enable `verbose` * azure coverage * Name * Trigger CI * Use `basename` * Trigger CI * Try `runInBand` * try `maxWorkers` Co-authored-by: Georgii Dolzhykov <thorn.mailbox@gmail.com>
4.3 KiB
4.3 KiB
Opinionated Code Formatter
JavaScript
· TypeScript
· Flow
· JSX
· JSON
CSS
· SCSS
· Less
HTML
· Vue
· Angular
GraphQL
· Markdown
· YAML
Your favorite language?
Intro
Prettier is an opinionated code formatter. It enforces a consistent style by parsing your code and re-printing it with its own rules that take the maximum line length into account, wrapping code when necessary.
Input
foo(reallyLongArg(), omgSoManyParameters(), IShouldRefactorThis(), isThereSeriouslyAnotherOne());
Output
foo(
reallyLongArg(),
omgSoManyParameters(),
IShouldRefactorThis(),
isThereSeriouslyAnotherOne()
);
Prettier can be run in your editor on-save, in a pre-commit hook, or in CI environments to ensure your codebase has a consistent style without devs ever having to post a nit-picky comment on a code review ever again!
Badge
Show the world you're using Prettier →
[](https://github.com/prettier/prettier)
Contributing
See CONTRIBUTING.md.
