From 02bfd4b341b584bcaf6dc85d10662078bb264db3 Mon Sep 17 00:00:00 2001 From: Matt Kantor Date: Tue, 9 Apr 2019 11:50:51 -0700 Subject: [PATCH] docs(eslint-plugin): `as const` with no-object-literal-type-assertion This doc change was overlooked when the feature was added in b70c283. --- .../docs/rules/no-object-literal-type-assertion.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/packages/eslint-plugin/docs/rules/no-object-literal-type-assertion.md b/packages/eslint-plugin/docs/rules/no-object-literal-type-assertion.md index b81ae0d87b69..044c68aa57fd 100644 --- a/packages/eslint-plugin/docs/rules/no-object-literal-type-assertion.md +++ b/packages/eslint-plugin/docs/rules/no-object-literal-type-assertion.md @@ -1,6 +1,6 @@ # Forbids an object literal to appear in a type assertion expression (no-object-literal-type-assertion) -Always prefer `const x: T = { ... };` to `const x = { ... } as T;`. Casting to `any` and `unknown` is still allowed. +Always prefer `const x: T = { ... };` to `const x = { ... } as T;`. Casting to `any` and `unknown` is still allowed, and const assertions (`as const`) are still allowed. ## Rule Details