Browse Source

set up cspell (#6684)

* set up cspell

* fix actual misspellings

* add cspell.json to .prettierignore

* rebase and fix issues in CHANGELOG.unreleased.md
master
Georgii Dolzhykov 3 years ago
committed by GitHub
parent
commit
69b481758c
No known key found for this signature in database GPG Key ID: 4AEE18F83AFDEB23
  1. 2
      .azure-pipelines/jobs/dev-lint.yml
  2. 1
      .prettierignore
  3. 59
      CHANGELOG.unreleased.md
  4. 396
      cspell.json
  5. 3
      package.json
  6. 2
      scripts/release/steps/check-git-status.js
  7. 2
      scripts/release/steps/publish-to-npm.js
  8. 2
      website/blog/2017-06-03-1.4.0.md
  9. 4
      website/blog/2017-11-07-1.8.0.md
  10. 10
      website/blog/2018-01-10-1.10.0.md
  11. 4
      website/blog/2018-02-26-1.11.0.md
  12. 2
      website/blog/2018-04-11-1.12.0.md
  13. 2
      website/blog/2018-05-27-1.13.0.md
  14. 4
      website/blog/2018-07-29-1.14.0.md
  15. 2
      website/blog/2019-01-20-1.16.0.md

2
.azure-pipelines/jobs/dev-lint.yml

@ -7,3 +7,5 @@ steps:
displayName: "Lint code"
- script: yarn lint-docs
displayName: "Lint docs"
- script: yarn spellcheck
displayName: "Spellcheck"

1
.prettierignore

@ -1 +1,2 @@
dist/
cspell.json

59
CHANGELOG.unreleased.md

@ -44,13 +44,11 @@ const link = <a href="example.com">http://example.com</a>;
-->
#### API: add resolveConfig option to getFileInfo() ([#6666] by [@kaicataldo])
#### API: Add `resolveConfig` option to `getFileInfo()` ([#6666] by [@kaicataldo])
Add a `resolveConfig: boolean` option to `prettier.getFileInfo()` that, when set to `true`, will resolve the configuration for the given file path. This allows consumers to take any overridden parsers into account.
#### JavaScript: add support for PartialApplication ([#6397] by [@JounQin])
Previous versions would not be able to format this syntax, this has been fixed in this version.
#### JavaScript: Add support for [partial application syntax](https://github.com/tc39/proposal-partial-application) ([#6397] by [@JounQin])
<!-- prettier-ignore -->
```js
@ -84,7 +82,7 @@ addTen(2); // 12
let newScore = player.score |> add(7, ?) |> clamp(0, 100, ?); // shallow stack, the pipe to \`clamp\` is the same frame as the pipe to \`add\`.
```
#### JavaScript: More readable parentheses for new-call ([#6412] by [@bakkot])
#### JavaScript: More readable parentheses for `new` call ([#6412] by [@bakkot])
<!-- prettier-ignore -->
```js
@ -314,11 +312,11 @@ Previously, Prettier added line breaks between text and mustaches which resulted
<!-- prettier-ignore -->
```hbs
// Input
<!-- Input -->
<p>Your username is @{{name}}</p>
<p>Hi {{firstName}} {{lastName}}</p>
// Output (Prettier stable)
<!-- Output (Prettier stable) -->
<p>
Your username is @
{{name}}
@ -329,7 +327,7 @@ Previously, Prettier added line breaks between text and mustaches which resulted
{{lastName}}
</p>
// Output (Prettier master)
<!-- Output (Prettier master) -->
<p>
Your username is @{{name}}
</p>
@ -344,7 +342,7 @@ Previously, Prettier would sometimes ignore whitespace when formatting comments.
<!-- prettier-ignore -->
```hbs
// Input
<!-- Input -->
<div>
{{! Foo }}
{{#if @foo}}
@ -357,7 +355,7 @@ Previously, Prettier would sometimes ignore whitespace when formatting comments.
{{/if}}
</div>
// Output (Prettier stable)
<!-- Output (Prettier stable) -->
<div>
{{! Foo }}
{{#if @foo}}
@ -367,7 +365,7 @@ Previously, Prettier would sometimes ignore whitespace when formatting comments.
{{/if}}
</div>
// Output (Prettier master)
<!-- Output (Prettier master) -->
<div>
{{! Foo }}
{{#if @foo}}
@ -380,7 +378,7 @@ Previously, Prettier would sometimes ignore whitespace when formatting comments.
</div>
```
#### JavaScript: Update ?? precedence to match stage 3 proposal ([#6404] by [@vjeux])
#### JavaScript: Update `??` precedence to match stage 3 proposal ([#6404] by [@vjeux])
We've updated Prettier's support for the nullish coalescing operator to match a spec update that no longer allows it to immediately contain, or be contained within an `&&` or `||` operation.
@ -445,8 +443,7 @@ source$
However, this heuristic caused people to complain because of false positives
where calls to functions or methods matching the hard-coded names would always
be split on multiple lines, even if the calls did not contain function
arguments (https://github.com/prettier/prettier/issues/5769,
https://github.com/prettier/prettier/issues/5969). For many, this blanket
arguments ([#5769](https://github.com/prettier/prettier/issues/5769), [#5969](https://github.com/prettier/prettier/issues/5969)). For many, this blanket
decision to split functions based on name was both surprising and sub-optimal.
We now use a refined heuristic which uses the presence of function literals to
@ -478,17 +475,17 @@ eventStore.update(id, _.flow(updater, incrementVersion));
<!-- prettier-ignore -->
```hbs
// Input
<!-- Input -->
<p>
Some escaped characters: &lt; &gt; &amp;
</p>
// Output (Prettier stable)
<!-- Output (Prettier stable) -->
<p>
Some escaped characters: < > &
</p>
// Output (Prettier master)
<!-- Output (Prettier master) -->
<p>
Some escaped characters: &lt; &gt; &amp;
</p>
@ -559,25 +556,25 @@ Previously, even if the line length was shorter than `printWidth`, Prettier woul
<!-- prettier-ignore -->
```html
// Input
<!-- Input -->
<template>
<template>foo</template>
</template>
// Output (Prettier stable)
<!-- Output (Prettier stable) -->
<template>
<template
>foo</template
>
</template>
// Output (Prettier master)
<!-- Output (Prettier master) -->
<template>
<template>foo</template>
</template>
```
#### JavaScript: Fix breaks indentation and idempotency when an arrow function that args include object pattern is passed to a function as parameter. ([#6301] & [#6382] by [@sosukesuzuki])
#### JavaScript: Empty lines in destructured arrow function parameters could break indentation and idempotence ([#6301] & [#6382] by [@sosukesuzuki])
Previously, Prettier indented code strangely when an arrow function whose parameters included an object pattern was passed to a function call as an argument. Also, it broke idempotence. Please see [#6294](https://github.com/prettier/prettier/issues/6294) for details.
@ -860,13 +857,13 @@ Previously, the flag was not applied on HTML attributes.
<!-- prettier-ignore-->
```hbs
// Input
<!-- Input -->
<div class="a-class-name"></div>
// Prettier (stable with the option --single-quote)
<!-- Prettier (stable with the option --single-quote) -->
<div class="a-class-name"></div>
// Prettier (master with the option --single-quote)
<!-- Prettier (master with the option --single-quote) -->
<div class='a-class-name'></div>
```
@ -1043,11 +1040,11 @@ class A {
#### Handlebars: Fix handling of whitespace and line breaks ([#6354] by [@chadian])
This fixes a variety of whitespace and line break usecases within handlebars and Glimmer templates.
This fixes a variety of whitespace and line break use cases within Handlebars and Glimmer templates.
<!-- prettier-ignore -->
```hbs
// Input
<!-- Input -->
<SomeComponent />{{name}}
Some sentence with {{dynamic}} expressions.
@ -1057,7 +1054,7 @@ Some sentence with {{dynamic}} expressions.
sometimes{{nogaps}}areimportant<Hello></Hello>
{{name}} is your name
// Output (Prettier stable)
<!-- Output (Prettier stable) -->
<SomeComponent />
{{name}}
Some sentence with
@ -1073,7 +1070,7 @@ areimportant
{{name}}
is your name
// Output (Prettier master)
<!-- Output (Prettier master) -->
<SomeComponent />{{name}}
Some sentence with {{dynamic}} expressions.
@ -1085,6 +1082,7 @@ sometimes{{nogaps}}areimportant
{{name}} is your name
```
[#5682]: https://github.com/prettier/prettier/pull/5682
[#5910]: https://github.com/prettier/prettier/pull/5910
[#6033]: https://github.com/prettier/prettier/pull/6033
[#6186]: https://github.com/prettier/prettier/pull/6186
@ -1100,8 +1098,10 @@ sometimes{{nogaps}}areimportant
[#6307]: https://github.com/prettier/prettier/pull/6307
[#6332]: https://github.com/prettier/prettier/pull/6332
[#6340]: https://github.com/prettier/prettier/pull/6340
[#6354]: https://github.com/prettier/prettier/pull/6354
[#6377]: https://github.com/prettier/prettier/pull/6377
[#6381]: https://github.com/prettier/prettier/pull/6381
[#6382]: https://github.com/prettier/prettier/pull/6382
[#6397]: https://github.com/prettier/prettier/pull/6397
[#6404]: https://github.com/prettier/prettier/pull/6404
[#6411]: https://github.com/prettier/prettier/pull/6411
@ -1119,8 +1119,8 @@ sometimes{{nogaps}}areimportant
[#6605]: https://github.com/prettier/prettier/pull/6605
[#6640]: https://github.com/prettier/prettier/pull/6640
[#6646]: https://github.com/prettier/prettier/pull/6646
[#6666]: https://github.com/prettier/prettier/pull/6666
[#6673]: https://github.com/prettier/prettier/pull/6673
[#6382]: https://github.com/prettier/prettier/pull/6382
[@brainkim]: https://github.com/brainkim
[@duailibe]: https://github.com/duailibe
[@gavinjoyce]: https://github.com/gavinjoyce
@ -1136,3 +1136,4 @@ sometimes{{nogaps}}areimportant
[@vjeux]: https://github.com/vjeux
[@selvazhagan]: https://github.com/selvazhagan
[@chadian]: https://github.com/chadian
[@kaicataldo]: https://github.com/kaicataldo

396
cspell.json

@ -0,0 +1,396 @@
{
"version": "0.1",
"words": [
"ACMR",
"Amjad",
"Andrey",
"apos",
"aquibm",
"arduner",
"arrayify",
"Artem",
"Ascher",
"ASTs",
"atrule",
"atrules",
"atword",
"autocmd",
"autocrlf",
"autodetects",
"autofix",
"autogenerated",
"autolink",
"autolinks",
"autoloading",
"Azzola",
"backport",
"backticks",
"bakkot",
"behaviour",
"Bekkelund",
"belochub",
"benjie",
"Bento",
"bigint",
"binaryish",
"bindon",
"bitshift",
"blenda",
"blockquote's",
"bookmarklet",
"bopomofo",
"brainkim",
"Breakell",
"Brevik",
"bugfix",
"bugfixes",
"builtins",
"callees",
"camelcase",
"camelified",
"chedeau",
"chrzosel",
"Clemmons",
"cliify",
"cloudflare",
"cmds",
"codebases",
"codeblock",
"codeblocks",
"codecov",
"codemirror",
"codemod",
"codemods",
"combinator",
"commonmark",
"concating",
"cond",
"cosmiconfig",
"CRLFs",
"daleroy",
"danez",
"dangmai",
"Dara",
"dashify",
"dcyriller",
"declarators",
"dedent",
"defun",
"deopt",
"deps",
"destructured",
"desugared",
"devs",
"docblock",
"docblocks",
"Dodds",
"dotfile",
"dotfiles",
"duailibe",
"Duperron",
"editorconfig",
"ekkhus",
"elektronik",
"Eneman",
"ericsakmar",
"Ericsburgh",
"Esben",
"esbenp",
"eslint's",
"eslump",
"esproposal",
"estree",
"esutils",
"eval",
"evilebottnawi",
"execa",
"fbglyph",
"Ficarra",
"filepath",
"Filipe",
"finalizer",
"Fiorini",
"flxwu",
"fnames",
"formatprg",
"Friedly",
"fuzzer",
"gavinjoyce",
"gettin",
"git's",
"gitattributes",
"githook",
"gitignore",
"Gitter",
"glimmerjs",
"globbing",
"globby",
"gofmt",
"googlegroups",
"googlemaps",
"Gregor",
"hackily",
"haggholm",
"Hampus",
"hardcoded",
"hardline",
"hardlines",
"harel",
"hashbang",
"Hawken",
"Hengles",
"Hersevoort",
"hlsson",
"hongrich",
"Horky",
"hotpink",
"hsla",
"htmlhint",
"hugomrdias",
"hwba",
"iarna",
"ICSS",
"idempotence",
"IIFE",
"IIFEs",
"ikatyang",
"Ilya",
"impltype",
"importee",
"importmap",
"indentable",
"indexof",
"instanceof",
"Intelli",
"intrinsics",
"jackyho",
"Jakefile",
"jakegavin",
"jbrown",
"jetbrains",
"jlongster",
"jnwng",
"Joar",
"josephfrazier",
"Joun",
"jounqin",
"jridgewell",
"jscodefmt",
"jsesc",
"jsfmt",
"JSXs",
"junit",
"jwbay",
"kachkaev",
"kalmanb",
"Karimov",
"Kassens",
"Kasturi",
"Kearney",
"keyof",
"Khatri",
"koba",
"libdef",
"linearize",
"linebreak",
"linebreaks",
"literalline",
"literallines",
"lockfile",
"loglevel",
"lowercased",
"lowercasing",
"lydell",
"malcolmsgroves",
"Marek",
"Masad",
"Matejka",
"Mateusz",
"mattiaerre",
"matzkoh",
"MDAST",
"memberish",
"memoized",
"Michał",
"microsyntax",
"Mikael",
"minimise",
"miniprettier",
"mitermayer",
"mixins",
"mjml",
"Moeller",
"Monteiro",
"Morrell",
"motiz",
"mousedown",
"mouseup",
"mprettier",
"multiparser",
"Muntean",
"nargs",
"neoclide",
"neoformat",
"neovim",
"nicolo",
"nnoremap",
"nodir",
"nonenumerable",
"nonspacing",
"normalise",
"normalised",
"nrvtbfux",
"nullability",
"nullish",
"Nuno",
"nvim",
"Okazaki",
"Okonetchnikov",
"oneth",
"onurtemizkan",
"onwarn",
"Oopsy",
"overparenthesization",
"packagejson",
"Panasenko",
"Pangsakulyanont",
"papayawhip",
"paren",
"parens",
"parentless",
"parser's",
"pcss",
"Pierzchała",
"Pieter",
"pomber",
"postprocess",
"postprocessor",
"precommit",
"prefetch",
"preorder",
"Prettier's",
"Prettier’s",
"prettierformatsource",
"prettiergetsupportinfo",
"prettierignore",
"prettierrc",
"prettylint",
"progid",
"promisify",
"proto",
"quasis",
"quux",
"Raghuvir",
"Rasmus",
"Rattray",
"rattrayalex",
"React's",
"readline",
"readlines",
"rebeccapurple",
"recurse",
"recurses",
"refmt",
"regexes",
"reimplement",
"repo",
"repo's",
"repos",
"reselect",
"rhengles",
"ribaudo",
"rreverser",
"ruleset",
"Sapegin",
"sbdchd",
"schemastore",
"serializer",
"setlocal",
"shellscape",
"shellsession",
"Shigeaki",
"Shinigami",
"Simen",
"singleline",
"skratchdot",
"smirea",
"socio",
"softline",
"softlines",
"Sorin",
"sosukesuzuki",
"squidfunk",
"srcset",
"Stachowiak",
"staged's",
"standalones",
"Stankiewicz",
"stringify",
"stubailo",
"styleguides",
"stylelint",
"stylelintrc",
"subvalue",
"suchipi",
"superset",
"supertypes",
"swac",
"tdeekens",
"templating",
"tempy",
"tgriesser",
"Tomasek",
"Tradeshift",
"Transloadit",
"TSAs",
"tsep",
"Typeahead",
"typecasted",
"typeof",
"udbff",
"udfff",
"uffff",
"Umidbek",
"unaries",
"uncheck",
"uncook",
"uniqby",
"unist",
"unparenthesised",
"unparenthesized",
"unparseable",
"unpause",
"unrestrict",
"untracked",
"valourous",
"Vanderwerff",
"vanguarding",
"versary",
"vimrc",
"vjeux",
"vjeux's",
"vnopts",
"Voyer",
"Vue's",
"Wadler",
"Wadler's",
"warrenseine",
"webstorm",
"whitespaces",
"xargs",
"yamafaktory",
"Yatharth",
"youtube",
"yuchi",
"Zatorski",
"Zeit",
"zimme",
"Zosel"
],
"ignoreRegExpList": [
"<!-- prettier-ignore -->\\n(`{3,})\\w*\\n[\\s\\S]+?\\1",
"\\[@\\w+?\\]",
"\\[`\\w+`\\]",
"ve+r+y+(long\\w+)?"
]
}

3
package.json

@ -127,6 +127,7 @@
"lint-dist": "eslint --no-eslintrc --no-ignore --env=browser \"dist/!(bin-prettier|index|third-party).js\"",
"build": "node --max-old-space-size=3072 ./scripts/build/build.js",
"build-docs": "node ./scripts/build-docs.js",
"check-deps": "node ./scripts/check-deps.js"
"check-deps": "node ./scripts/check-deps.js",
"spellcheck": "npx cspell {bin,scripts,src}/**/*.js {docs,website/blog}/**/*.md CHANGELOG.unreleased.md"
}
}

2
scripts/release/steps/check-git-status.js

@ -7,7 +7,7 @@ module.exports = async function() {
if (status) {
throw Error(
"Uncommited local changes. " +
"Uncommitted local changes. " +
"Please revert or commit all local changes before making a release."
);
}

2
scripts/release/steps/publish-to-npm.js

@ -29,7 +29,7 @@ module.exports = async function({ dry, version }) {
- Copy release notes from {yellow CHANGELOG.md}
- Press {bgGreen.black Publish release }
{bold.underline Test the new releae}
{bold.underline Test the new release}
- In a new session, run {yellow npm i prettier@latest} in another directory
- Test the API and CLI

2
website/blog/2017-06-03-1.4.0.md

@ -432,7 +432,7 @@ var numberValue1 = 1,
#### Inline | null and | void ([#1734](https://github.com/prettier/prettier/pull/1734))
The expanded version of flow union looks good when they are many objects but if it's used for nullability, the it looks very weird. We're now inlining `| null` and `| void`.
The expanded version of flow union looks good when they are many objects but if it's used for nullability, then it looks very weird. We're now inlining `| null` and `| void`.
<!-- prettier-ignore -->
```ts

4
website/blog/2017-11-07-1.8.0.md

@ -210,7 +210,7 @@ This operator is similar to `||` except it only evaluates the right-hand-side if
const foo = object.foo ?? "default";
```
#### Improved template literal expresions line breaks ([#3124](https://github.com/prettier/prettier/pull/3124)) by [@duailibe](https://github.com/duailibe)
#### Improved template literal expressions line breaks ([#3124](https://github.com/prettier/prettier/pull/3124)) by [@duailibe](https://github.com/duailibe)
This was another known issue with Prettier, when printing a template literal string with expressions inside that went over the print width, it would wrap the code in weird places inside the expressions. Now, if Prettier needs to insert a line break, it should happen right between `${` and `}`.
@ -407,7 +407,7 @@ function functionName() {
}
```
#### Fix array acessors in method chains ([#3137](https://github.com/prettier/prettier/pull/3137)) by [@duailibe](https://github.com/duailibe)
#### Fix array accessors in method chains ([#3137](https://github.com/prettier/prettier/pull/3137)) by [@duailibe](https://github.com/duailibe)
In a method chain we split lines by grouping elements together and accessing an array should be printed in the end of a group instead of the beginning.

10
website/blog/2018-01-10-1.10.0.md

@ -12,7 +12,7 @@ It's also an exciting release in itself because Prettier now has partial support
## Retrospective
Ever since gofmt came out in 2013, I ([@vjeux]) became obsessed with the idea of automatic formatting. I started seeing problems that would be solved by an automatic formatter all the time: arguing about coding style, having to manually format the code manually, difficulty to write codemod tools…
Ever since gofmt came out in 2013, I ([@vjeux]) became obsessed with the idea of automatic formatting. I started seeing problems that would be solved by an automatic formatter all the time: arguing about coding style, having to format the code manually, difficulty to write codemod tools…
When last December there were not one but two people independently working on a JavaScript pretty printer, it was a sign! Pieter Vanderwerff built one in Reason based on Flow infrastructure and James Long in JavaScript. I played the role of a cheerleader by setting up the same test suite for the two projects as well as running their pretty printer on existing codebases and extracting lists of [things that](https://github.com/prettier/prettier/issues/2) were [not printed well](https://github.com/prettier/prettier/issues/6).
@ -98,7 +98,7 @@ Check [the docs][plugin api] for more information.
#### Support numeric separators ([#3580]) by [@azz]
Numeric seperators are a [stage 3 ECMAScript proposal](https://github.com/tc39/proposal-numeric-separator). Support has been added for them in TypeScript 2.7, and Prettier will now preserve them.
Numeric separators are a [stage 3 ECMAScript proposal](https://github.com/tc39/proposal-numeric-separator). Support has been added for them in TypeScript 2.7, and Prettier will now preserve them.
<!-- prettier-ignore -->
```ts
@ -168,7 +168,7 @@ type SomeType = {
#### Inline do expressions inside of JSX ([#3607]) by [@vjeux]
"Do expressions" are a [stage 1 ECMAScript proposal](https://github.com/tc39/proposal-do-expressions), and they're particularly useful in JSX, however the extra level of indentation isn't required, so we've inlined them into the expresssion container.
"Do expressions" are a [stage 1 ECMAScript proposal](https://github.com/tc39/proposal-do-expressions), and they're particularly useful in JSX, however the extra level of indentation isn't required, so we've inlined them into the expression container.
<!-- prettier-ignore -->
```jsx
@ -287,7 +287,7 @@ type Foo {
}
```
Ommitting `{}` when there is no content.
Omitting `{}` when there is no content.
<!-- prettier-ignore -->
```gql
@ -408,7 +408,7 @@ $ prettier --loglevel silent --write test.js
#### Output files as-is if ignored ([#3618]) by [@duailibe]
We've fixed up the behavior of the CLI when it comes to ignored files. Previously when a file was ignored by `.prettierignore`, the CLI would ouput nothing. This affected editor integrations. The behaviour is now:
We've fixed up the behavior of the CLI when it comes to ignored files. Previously when a file was ignored by `.prettierignore`, the CLI would output nothing. This affected editor integrations. The behaviour is now:
- With `--write`, don't read or write to the ignored file.
- Without `--write`, read the ignored file and output as-is.

4
website/blog/2018-02-26-1.11.0.md

@ -10,7 +10,7 @@ Since the last release, the [Prettier website](https://prettier.io) has gotten a
### Facebook is 💯% Prettier
Another exciting announcement is that all the JavaScript files in the Facebook codebase have now been converted to Prettier! What's mindblowing is that there hasn't been a concerted push to convert the codebase to Prettier, we just added the tooling in place and documentation on how to migrate a folder to Prettier and people just started converting their piece of the codebase.
Another exciting announcement is that all the JavaScript files in the Facebook codebase have now been converted to Prettier! What's mind-blowing is that there hasn't been a concerted push to convert the codebase to Prettier, we just added the tooling in place and documentation on how to migrate a folder to Prettier and people just started converting their piece of the codebase.
In 8 months, 75% of the codebase was organically converted and last week we did a final push to convert the rest and enforce that every file from now on is using Prettier! It shows that Prettier is robust to support all the crazy edge cases you can imagine and also that it provides a lot of value given the crazy adoption rate.
@ -1077,7 +1077,7 @@ This was not intended to be allowed, and has been reverted (in this case, you wo
#### Respect EditorConfig when `--config` is passed ([#3992] by [@josephfrazier])
This is a minor change to the the way `.editorignore` files are handled. Previously when `--config` was provided, `.editorconfig` was ignored.
This is a minor change to the the way `.editorconfig` files are handled. Previously when `--config` was provided, `.editorconfig` was ignored.
---

2
website/blog/2018-04-11-1.12.0.md

@ -645,7 +645,7 @@ In Prettier 1.11.1, HTML nested underneath a list item was not formatted correct
#### Print literalline for newline instead of hardline ([#4083](https://github.com/prettier/prettier/pull/4083) by [@ikatyang](https://github.com/ikatyang))
In Prettier 1.11.1, when embedding CSS or JSX in markdown, there was an issue that caused the indentation level of block comments to be set incorrectly in some sitautions. This issue has been fixed in Prettier 1.12.0:
In Prettier 1.11.1, when embedding CSS or JSX in markdown, there was an issue that caused the indentation level of block comments to be set incorrectly in some situations. This issue has been fixed in Prettier 1.12.0:
<!-- prettier-ignore -->
``````md

2
website/blog/2018-05-27-1.13.0.md

@ -62,7 +62,7 @@ You can read more about this in the [Plugin docs](https://prettier.io/docs/en/pl
#### Improve cursor offset tracking ([#4397] by [@ds300])
Prettier 1.13 vastly improves the cursor offset tracking for several cases where Prettier was outputing the wrong location, making editor integrations move the cursor to an incorrect location.
Prettier 1.13 vastly improves the cursor offset tracking for several cases where Prettier was outputting the wrong location, making editor integrations move the cursor to an incorrect location.
### JavaScript

4
website/blog/2018-07-29-1.14.0.md

@ -548,7 +548,7 @@ Output: (Prettier 1.14)
The core feature of Prettier is to wrap lines when they go past the print width,
and to do this we need to calculate the visual width of every character.
The easiest way to count them is by using JavaScript’s `String#length` property
but some non-ASCII characters like CJK characters have widths larger than a Latin characer.
but some non-ASCII characters like CJK characters have widths larger than a Latin character.
As a workaround, we replaced those 2-char-wide characters with 2 spaces before calculating the string’s length.
This works fine but it also slows down Prettier because we have to run the replacement on every token.
In Prettier 1.14, we check if the string contains only ASCII characters
@ -885,7 +885,7 @@ In Prettier 1.14, email autolinks are preserved.
In Prettier 1.12, we added the support for fenced codeblock lang followed by attributes,
which requires them to be separated by whitespaces.
But this introduced the inconsistency for codeblock highlighting in Atom that
codeblocks are hightlighted but we do not format them.
codeblocks are highlighted but we do not format them.
We updated our detection logic in Prettier 1.14 so they should behave the same now.
<!-- prettier-ignore -->

2
website/blog/2019-01-20-1.16.0.md

@ -503,7 +503,7 @@ will format it.
Previously, the quotes around HTML attribute values were always printed as double
quotes. To improve readability, they are now printed as the quote type that results
in fewer escape characters being requiered in the string, like we do for other strings.
in fewer escape characters being required in the string, like we do for other strings.
<!-- prettier-ignore -->
```html

Loading…
Cancel
Save