From eb05832ee82627a41794aee09ddf85c1ff26a62f Mon Sep 17 00:00:00 2001
From: yassin-kammoun-sonarsource <yassin.kammoun@sonarsource.com>
Date: Mon, 28 Feb 2022 12:37:40 +0100
Subject: [PATCH] Fix 'future-reserved-words' unit tests: explicitly allow
 parsing reserved words

See https://github.com/eslint/eslint/releases/tag/v8.0.0
See https://github.com/eslint/eslint/pull/15046
---
 eslint-bridge/tests/rules/future-reserved-words.test.ts | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/eslint-bridge/tests/rules/future-reserved-words.test.ts b/eslint-bridge/tests/rules/future-reserved-words.test.ts
index 672ece6ee6..71088ee4c0 100644
--- a/eslint-bridge/tests/rules/future-reserved-words.test.ts
+++ b/eslint-bridge/tests/rules/future-reserved-words.test.ts
@@ -19,7 +19,9 @@
  */
 import { RuleTester } from 'eslint';
 
-const ruleTester = new RuleTester({ parserOptions: { ecmaVersion: 3, sourceType: 'script' } });
+const ruleTester = new RuleTester({
+  parserOptions: { ecmaVersion: 3, sourceType: 'script', allowReserved: true },
+});
 import { rule } from 'rules/future-reserved-words';
 
 ruleTester.run('Future reserved words', rule, {