diff --git a/changelog_unreleased/angular/17534.md b/changelog_unreleased/angular/17534.md index 55e22a69d..f53e323d1 100644 --- a/changelog_unreleased/angular/17534.md +++ b/changelog_unreleased/angular/17534.md @@ -15,7 +15,7 @@ {{ void(1 + 2) }} // Prettier stable -The new syntax not corretly recognized. +The new syntax is not correctly recognized. // Prettier main {{ a in b }} diff --git a/changelog_unreleased/api/17166.md b/changelog_unreleased/api/17166.md index 41671a113..44d42f9b9 100644 --- a/changelog_unreleased/api/17166.md +++ b/changelog_unreleased/api/17166.md @@ -1,6 +1,6 @@ #### Accept `URL` in `plugins` option (#17166 by @fisker) -`plugins` option now accepts [URL](https://developer.mozilla.org/en-US/docs/Web/API/URL) with `file:` protocol or url string starts with `file:` in all public APIs. +`plugins` option now accepts [URL](https://developer.mozilla.org/en-US/docs/Web/API/URL) with `file:` protocol or a url string that starts with `file:` in all public APIs. ```js // `URL` diff --git a/changelog_unreleased/api/17167.md b/changelog_unreleased/api/17167.md index 4c0e9f8f6..15e30d755 100644 --- a/changelog_unreleased/api/17167.md +++ b/changelog_unreleased/api/17167.md @@ -1,6 +1,6 @@ #### Accept `URL` as custom config file in `resolveConfig` (#17167 by @fisker) -[`prettier.resolveConfig()`](https://prettier.io/docs/api#prettierresolveconfigfileurlorpath--options) now accepts an [URL](https://developer.mozilla.org/en-US/docs/Web/API/URL) with `file:` protocol or a url string starts with `file:` as custom config file location. +[`prettier.resolveConfig()`](https://prettier.io/docs/api#prettierresolveconfigfileurlorpath--options) now accepts an [URL](https://developer.mozilla.org/en-US/docs/Web/API/URL) with `file:` protocol or a url string that starts with `file:` as custom config file location. ```js // `URL` diff --git a/changelog_unreleased/api/17178.md b/changelog_unreleased/api/17178.md index 7dd5fe243..3c2d82eec 100644 --- a/changelog_unreleased/api/17178.md +++ b/changelog_unreleased/api/17178.md @@ -2,9 +2,9 @@ `*.frag` was interpreted as JavaScript files, but `.frag` is also used in GLSL([OpenGL Shading Language](https://en.wikipedia.org/wiki/OpenGL_Shading_Language)). It causes error when Prettier try to format them as JavaScript files. -Since Prettier main, `*.frag` files except `*.start.frag`, `*.end.frag`, `start.frag`, and `end.frag` no longer treat as JavaScript files. +Since Prettier main, `*.frag` files except `*.start.frag`, `*.end.frag`, `start.frag`, and `end.frag` are no longer treated as JavaScript files. -If you have JavaScript files with `.frag` not match patterns mentioned above, you can config with `overrides`. +If you have JavaScript files with `.frag` that do not match the patterns mentioned above, you can config with `overrides`. ```js export default { diff --git a/changelog_unreleased/api/17331.md b/changelog_unreleased/api/17331.md index e96ec006d..3c4eede57 100644 --- a/changelog_unreleased/api/17331.md +++ b/changelog_unreleased/api/17331.md @@ -1,6 +1,6 @@ #### Add `isSupported` function support for `languages` API (#17331 by @JounQin, #17490 by @fisker) -Previously, `languages` API for custom plugin only supported to infer parser based on the file basename or extension. +Previously, `languages` API for custom plugins only supported inferring parser based on the file basename or extension. Prettier main added `isSupported: (options: { filepath: string }) => boolean` function to allow plugin check if file is supported based on the full path (eg: files in a specific directory). @@ -11,7 +11,7 @@ When using from APIs(eg: `prettier.format()`), Prettier can not ensure it's a va ::: -If no `isSupported` provided, it just behaviors the same way as before. +If no `isSupported` provided, it just behaves the same way as before. ```js export const languages = [ diff --git a/changelog_unreleased/api/17548.md b/changelog_unreleased/api/17548.md index d3c6bf6fe..860245fe2 100644 --- a/changelog_unreleased/api/17548.md +++ b/changelog_unreleased/api/17548.md @@ -1,6 +1,6 @@ #### Fix plugin loading in `prettier.getFileInfo()` (#17548 by @fisker) -In previous version, `prettier.getFileInfo()` only read `parser` config from `.prettierrc`, but doesn't load plugin to infer parser from plugin `languages`, Prettier main fixed it. +In previous version, `prettier.getFileInfo()` only read `parser` config from `.prettierrc`, but doesn't load plugins to infer parser from plugin `languages`, Prettier main fixed it. ```js // prettier-plugin-foo diff --git a/changelog_unreleased/cli/17151.md b/changelog_unreleased/cli/17151.md index 96f2692d1..2340bc74e 100644 --- a/changelog_unreleased/cli/17151.md +++ b/changelog_unreleased/cli/17151.md @@ -1,6 +1,6 @@ #### [HIGHLIGHT] Support experimental CLI (#17151, #17396 by @fisker) -You may already heard or used our new [performance improved CLI](https://prettier.io/blog/2023/11/30/cli-deep-dive). From prettier main, you can now use it without installing unstable v4 version. +You may have already heard of or used our new [performance improved CLI](https://prettier.io/blog/2023/11/30/cli-deep-dive). From prettier main, you can now use it without installing unstable v4 version. ```sh # Run CLI with `--experimental-cli` diff --git a/changelog_unreleased/cli/17438.md b/changelog_unreleased/cli/17438.md index b816c10a5..c87901366 100644 --- a/changelog_unreleased/cli/17438.md +++ b/changelog_unreleased/cli/17438.md @@ -1,3 +1,3 @@ #### Ignore file modified time when `--cache-strategy=content` (#17438 by @fisker) -In previous version, when using `--cache-strategy=content`, if the file modified time changed, it still get re-formatted even the file content didn't change, Prettier main fixed it. +In previous version, when using `--cache-strategy=content`, if the file modified time changed, it still gets re-formatted even the file content didn't change, Prettier main fixed it. diff --git a/changelog_unreleased/cli/17505.md b/changelog_unreleased/cli/17505.md index 4f24ba70d..80f9bda85 100644 --- a/changelog_unreleased/cli/17505.md +++ b/changelog_unreleased/cli/17505.md @@ -1,4 +1,4 @@ -#### Fix exitCode when parser can not infer (#17505 by @fisker) +#### Fix exitCode when parser cannot infer (#17505 by @fisker) ```console touch unknown diff --git a/changelog_unreleased/css/17362.md b/changelog_unreleased/css/17362.md index d604c822a..6ea918f2f 100644 --- a/changelog_unreleased/css/17362.md +++ b/changelog_unreleased/css/17362.md @@ -1,6 +1,6 @@ #### Support `@utility` directive for Tailwind (#17362 by @sosukesuzuki) -This changes supports `@utility` directive for Tailwind CSS V4. +This change supports `@utility` directive for Tailwind CSS V4. ```css diff --git a/changelog_unreleased/flow/17520.md b/changelog_unreleased/flow/17520.md index 083433486..f014dff42 100644 --- a/changelog_unreleased/flow/17520.md +++ b/changelog_unreleased/flow/17520.md @@ -2,7 +2,7 @@ `@prettier/plugin-hermes` is based on [Hermes JS Engine](https://github.com/facebook/hermes/blob/main/README.md). -This plugin include a new parser `hermes` (Flow syntax), to use this plugin: +This plugin includes a new parser `hermes` (Flow syntax), to use this plugin: 1. Install the plugin @@ -17,7 +17,7 @@ This plugin include a new parser `hermes` (Flow syntax), to use this plugin: - "@prettier/plugin-hermes" ``` -Due to package size limitation, this plugin is not included in the `prettier` package, it needs to be installed separately. +Due to package size limitations, this plugin is not included in the `prettier` package, it needs to be installed separately. **We plan to make this as the default parser for Flow syntax support in v4, we'll also remove `babel-flow` parser in v4, please give it a try.** diff --git a/changelog_unreleased/javascript/17145.md b/changelog_unreleased/javascript/17145.md index 3d77d0fd0..720b6f773 100644 --- a/changelog_unreleased/javascript/17145.md +++ b/changelog_unreleased/javascript/17145.md @@ -1,6 +1,6 @@ #### Add parentheses to `AssignmentExpression` in class property keys (#17145 by @fisker) -Previously we only add parentheses to `AssignmentExpression` in object keys, but not in class property keys. Thanks for [Biome](https://biomejs.dev/formatter/differences-with-prettier/#prettier-has-an-inconsistent-behavior-for-assignment-in-computed-keys) to bring our attention on this inconsistent. +Previously we only add parentheses to `AssignmentExpression` in object keys, but not in class property keys. Thanks to [Biome](https://biomejs.dev/formatter/differences-with-prettier/#prettier-has-an-inconsistent-behavior-for-assignment-in-computed-keys) for bringing our attention to this inconsistency. ```jsx diff --git a/changelog_unreleased/javascript/17190.md b/changelog_unreleased/javascript/17190.md index 5d2ab29e5..6d98d8875 100644 --- a/changelog_unreleased/javascript/17190.md +++ b/changelog_unreleased/javascript/17190.md @@ -1,10 +1,10 @@ #### Add parentheses to numbers in optional member expression (#17190 by @fisker) -There is a inconsistency when formatting member expression where the object is a number before Prettier main. +There is an inconsistency when formatting member expression where the object is a number before Prettier main. When using `babel` parser(and other Babel based parsers), we print the number as unparenthesized, when using `typescript` parser(and other ESTree parsers), we print it as parenthesized. -Technically parentheses are not needed, but if we print it as `1?.toString()` and later users realizes it's unnecessary to use `?.`, users can't simply remove the question mark because `1.toString()` will raise a `SyntaxError`, for this reason, we decide to always put parentheses around it. +Technically parentheses are not needed, but if we print it as `1?.toString()` and later users realize it's unnecessary to use `?.`, users can't simply remove the question mark because `1.toString()` will raise a `SyntaxError`, for this reason, we decide to always put parentheses around it. ```jsx diff --git a/changelog_unreleased/javascript/17363.md b/changelog_unreleased/javascript/17363.md index deb1374ca..fceb5e310 100644 --- a/changelog_unreleased/javascript/17363.md +++ b/changelog_unreleased/javascript/17363.md @@ -1,5 +1,5 @@ #### Removed support for experimental `Records & Tuples` (#17363 by @fisker) -The the ES proposal [JavaScript Records & Tuples Proposal](https://github.com/tc39/proposal-record-tuple) has been withdrawn. +The ES proposal [JavaScript Records & Tuples Proposal](https://github.com/tc39/proposal-record-tuple) has been withdrawn. - [Disclaimer about non-standard syntax](https://prettier.io/docs/en/rationale.html#disclaimer-about-non-standard-syntax) diff --git a/changelog_unreleased/javascript/17472.md b/changelog_unreleased/javascript/17472.md index 918169b86..3ed660964 100644 --- a/changelog_unreleased/javascript/17472.md +++ b/changelog_unreleased/javascript/17472.md @@ -2,7 +2,7 @@ `@prettier/plugin-oxc` is based on [OXC](https://oxc.rs/)(A **fast** JavaScript and TypeScript parser in Rust). -This plugin include two new parser `oxc` (JavaScript syntax) and `oxc-ts` (TypeScript syntax), to use this plugin: +This plugin includes two new parsers `oxc` (JavaScript syntax) and `oxc-ts` (TypeScript syntax), to use this plugin: 1. Install the plugin @@ -17,7 +17,7 @@ This plugin include two new parser `oxc` (JavaScript syntax) and `oxc-ts` (TypeS - "@prettier/plugin-oxc" ``` -Due to package size limitation, this plugin is not included in the `prettier` package, it needs to be installed separately. +Due to package size limitations, this plugin is not included in the `prettier` package, it needs to be installed separately. For more information, check [the package homepage](https://github.com/prettier/prettier/tree/main/packages/plugin-oxc).