Fix a TODO (#15902)

.github/workflows/lint.yml

@@ -53,8 +53,7 @@ jobs:
         run: yarn lint:blog
 
       - name: Lint docs code block
-        # TODO: Lint files in `website/versioned_docs/version-stable` too
+        run: yarn prettier "{docs,website/versioned_docs/version-stable}/**/*.md" --check
-        run: yarn "docs/**/*.md"
         env:
           # Make Prettier throws on embeded format
           PRETTIER_DEBUG: true

CHANGELOG.md

@@ -2053,7 +2053,7 @@ Test <a href="https://prettier.io">abc</a>.
 #### Fix broken format for `...infer T` ([#9044](https://github.com/prettier/prettier/pull/9044) by [@fisker](https://github.com/fisker))
 
 <!-- prettier-ignore -->
-```typescript
+```ts
 // Input
 type Tail<T extends any[]> = T extends [infer U, ...infer R] ? R : never;
 

docs/rationale.md

@@ -87,7 +87,7 @@ const user = {
 
 Just like with objects, decorators are used for a lot of different things. Sometimes it makes sense to write decorators _above_ the line they're decorating, sometimes it’s nicer if they're on the _same_ line. We haven’t been able to find a good rule for this, so Prettier keeps your decorator positioned like you wrote them (if they fit on the line). This isn’t ideal, but a pragmatic solution to a difficult problem.
 
-```js
+```ts
 @Component({
   selector: "hero-button",
   template: `<button>{{ label }}</button>`,
@@ -108,14 +108,14 @@ class HeroButtonComponent {
 There’s one exception: classes. We don’t think it ever makes sense to inline the decorators for them, so they are always moved to their own line.
 
 <!-- prettier-ignore -->
-```js
+```ts
 // Before running Prettier:
 @observer class OrderLine {
   @observable price: number = 0;
 }
 ```
 
-```js
+```ts
 // After running Prettier:
 @observer
 class OrderLine {
@@ -125,7 +125,7 @@ class OrderLine {
 
 Note: Prettier 1.14.x and older tried to automatically move your decorators, so if you've run an older Prettier version on your code you might need to manually join up some decorators here and there to avoid inconsistencies:
 
-```js
+```ts
 @observer
 class OrderLine {
   @observable price: number = 0;

website/blog/2017-12-05-1.9.0.md

@@ -220,7 +220,7 @@ const {
 We were omitting parens around type assertions inside decorators:
 
 <!-- prettier-ignore -->
-```typescript
+```ts
 @(bind as ClassDecorator)
 class Decorated {}
 ```

website/blog/2021-05-09-2.3.0.md

@@ -819,7 +819,7 @@ const x = async do {
 `typescript` parser only, `babel-ts` doesn't have this issue.
 
 <!-- prettier-ignore -->
-```typescript
+```ts
 // Input
 class Foo {
   bar() /* bat */;

website/versioned_docs/version-stable/rationale.md

@@ -88,7 +88,7 @@ const user = {
 
 Just like with objects, decorators are used for a lot of different things. Sometimes it makes sense to write decorators _above_ the line they're decorating, sometimes it’s nicer if they're on the _same_ line. We haven’t been able to find a good rule for this, so Prettier keeps your decorator positioned like you wrote them (if they fit on the line). This isn’t ideal, but a pragmatic solution to a difficult problem.
 
-```js
+```ts
 @Component({
   selector: "hero-button",
   template: `<button>{{ label }}</button>`,
@@ -109,14 +109,14 @@ class HeroButtonComponent {
 There’s one exception: classes. We don’t think it ever makes sense to inline the decorators for them, so they are always moved to their own line.
 
 <!-- prettier-ignore -->
-```js
+```ts
 // Before running Prettier:
 @observer class OrderLine {
   @observable price: number = 0;
 }
 ```
 
-```js
+```ts
 // After running Prettier:
 @observer
 class OrderLine {
@@ -126,7 +126,7 @@ class OrderLine {
 
 Note: Prettier 1.14.x and older tried to automatically move your decorators, so if you've run an older Prettier version on your code you might need to manually join up some decorators here and there to avoid inconsistencies:
 
-```js
+```ts
 @observer
 class OrderLine {
   @observable price: number = 0;