Directory

Comparing 2f6b916dd709...0221522f253e · WordPress/gutenberg · GitHub
Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: WordPress/gutenberg
base: 2f6b916dd709
Choose a base ref
...
head repository: WordPress/gutenberg
compare: 0221522f253e
Choose a head ref
  • 2 commits
  • 153 files changed
  • 5 contributors

Commits on Apr 30, 2024

  1. Eslint: Restore curly rule when using prettier 

    The `curly` eslint rule was disabled when using prettier. Some
configurations of the rule may conflict with prettier's autoformatting,
but the `all` option used in @wordpress/eslint-plugin does not.

This aligns with the WordPress JavaScript Standards:

> `if`, `else`, `for`, `while`, and `try` blocks should always use
> braces, and always go on multiple lines.

- WordPress JavaScript Standards: https://developer.wordpress.org/coding-standards/wordpress-coding-standards/javascript/#blocks-and-curly-braces
- `curly` rule description: https://eslint.org/docs/latest/rules/curly#rule-details

Co-authored-by: sirreal <jonsurrell@git.wordpress.org>
Co-authored-by: gziolo <gziolo@git.wordpress.org>
Co-authored-by: swissspidy <swissspidy@git.wordpress.org>
Co-authored-by: youknowriad <youknowriad@git.wordpress.org>
    @sirreal @gziolo
    @swissspidy @youknowriad
    5 people committed Apr 30, 2024
    Configuration menu
    Copy the full SHA
    d6226be View commit details
    Browse the repository at this point in the history

  2. Apply eslint autofix for curly rule violations

    @sirreal
    sirreal committed Apr 30, 2024
    Configuration menu
    Copy the full SHA
    0221522 View commit details
    Browse the repository at this point in the history