eslint/.github/ISSUE_TEMPLATE/new-rule.yml

   1 name: "\U0001F680 Propose a new core rule"
   2 description: "Propose a new rule to be added to the ESLint core"
   3 title: "New Rule: (fill in)"
   4 labels:
   5   - rule
   6   - feature
   7 body:
   8 - type: markdown
   9   attributes:
  10     value: By opening an issue, you agree to abide by the [Open JS Foundation Code of Conduct](https://eslint.org/conduct).
  11 - type: input
  12   attributes:
  13     label: Rule details
  14     description: What should the new rule do?
  15   validations:
  16     required: true
  17 - type: input
  18   attributes:
  19     label: Related ECMAScript feature
  20     description: What new ECMAScript feature does this rule relate to? Note that we only accept new core rules related to new ECMAScript features.
  21   validations:
  22     required: true
  23 - type: dropdown
  24   attributes:
  25     label: What type of rule is this?
  26     options:
  27       - Warns about a potential problem
  28       - Suggests an alternate way of doing something
  29       - Enforces a formatting/stylistic preference
  30   validations:
  31     required: true
  32 - type: textarea
  33   attributes:
  34     label: Example code
  35     description: Please provide some example JavaScript code that this rule will warn about. This field will render as JavaScript.
  36     render: js
  37   validations:
  38     required: true
  39 - type: textarea
  40   attributes:
  41     label: Why should this rule be in the core instead of a plugin?
  42     description: In general, we prefer that rules be implemented in plugins where they can be tailored to your specific use case.
  43   validations:
  44     required: true
  45 - type: checkboxes
  46   attributes:
  47     label: Participation
  48     options:
  49       - label: I am willing to submit a pull request to implement this rule.
  50         required: false
  51 - type: textarea
  52   attributes:
  53     label: Additional comments
  54     description: Is there anything else that's important for the team to know?