chore: remove what-comments and upstream references

Author: johanrd

lib/rules/template-require-form-method.js

@@ -26,9 +26,6 @@ function parseConfig(config) {
     }
   }
 
-  // Invalid configuration (e.g. unknown method in allowedMethods). Throw a
-  // descriptive error to surface the problem to the user rather than silently
-  // disabling the rule.
   throw new Error(
     'template-require-form-method: invalid configuration. Expected one of:\n' +
       '  * boolean - `true` to enable / `false` to disable\n' +

tests/lib/rules/template-require-form-method.js

@@ -9,8 +9,8 @@ const validHbs = [
     options: [{ allowedMethods: ['get'] }],
     code: '<form method="GET"></form>',
   },
-  // Default behavior: when no options are provided, the rule is disabled
-  // (matching upstream ember-template-lint). A bare <form> should NOT error.
+  // Default behavior: when no options are provided, the rule is disabled.
+  // A bare <form> should NOT error.
   '<form></form>',
   '<form method="NOT_A_VALID_METHOD"></form>',
   { options: [true], code: '<form method="POST"></form>' },
@@ -111,8 +111,8 @@ hbsRuleTester.run('template-require-form-method', rule, {
   invalid: invalidHbs,
 });
 
-// Upstream-aligned error-surfacing tests. parseConfig should throw on an
-// invalid `allowedMethods` entry rather than silently disabling the rule.
+// parseConfig should throw on an invalid `allowedMethods` entry so that
+// misconfiguration is surfaced immediately rather than silently ignored.
 describe('template-require-form-method invalid configuration', () => {
   const { Linter } = require('eslint');