[pve-eslint.git] / eslint / .github / ISSUE_TEMPLATE / NEW_RULE.md

---
name: "\U0001F680 New rule proposal"
about: Propose a new rule to be added to ESLint
title: ''
labels: triage, rule, feature
assignees: ''

---

<!--
    ESLint adheres to the Open JS Foundation Code of Conduct:
    https://eslint.org/conduct

    This template is for new rule proposals. If you are proposing a new rule, please continue on. If you are here for another reason, please see below:

    1. To report a bug: https://eslint.org/docs/developer-guide/contributing/reporting-bugs
    2. To request a rule change: https://eslint.org/docs/developer-guide/contributing/rule-changes
    3. To request a change that is not a bug fix, rule change, or new rule: https://eslint.org/docs/developer-guide/contributing/changes
    4. If you have any questions, please stop by our chatroom: https://eslint.org/chat

    Note that leaving sections blank will make it difficult for us to troubleshoot and we may have to close the issue.
-->


**Please describe what the rule should do:**


**What new ECMAScript feature does this rule relate to?**

<!-- New rules must be related to ECMAScript features added within the last 12 months -->

**What category of rule is this? (place an "X" next to just one item)**

[ ] Warns about a potential error (problem)
[ ] Suggests an alternate way of doing something (suggestion)
[ ] Other (please specify:)

**Provide 2-3 code examples that this rule will warn about:**

<!-- Put your code examples here -->
```js

```

**Why should this rule be included in ESLint (instead of a plugin)?**


**Are you willing to submit a pull request to implement this rule?**
Commit	Line	Data
eb39fafa DC	1	---
	2	name: "\U0001F680 New rule proposal"
	3	about: Propose a new rule to be added to ESLint
	4	title: ''
	5	labels: triage, rule, feature
	6	assignees: ''
	7
	8	---
	9
	10	<!--
ebb53d86 TL	11	ESLint adheres to the Open JS Foundation Code of Conduct:
ebb53d86 TL	12	https://eslint.org/conduct
eb39fafa DC	13
	14	This template is for new rule proposals. If you are proposing a new rule, please continue on. If you are here for another reason, please see below:
	15
	16	1. To report a bug: https://eslint.org/docs/developer-guide/contributing/reporting-bugs
	17	2. To request a rule change: https://eslint.org/docs/developer-guide/contributing/rule-changes
	18	3. To request a change that is not a bug fix, rule change, or new rule: https://eslint.org/docs/developer-guide/contributing/changes
ebb53d86	19	4. If you have any questions, please stop by our chatroom: https://eslint.org/chat
eb39fafa DC	20
	21	Note that leaving sections blank will make it difficult for us to troubleshoot and we may have to close the issue.
	22	-->
	23
ebb53d86	24
eb39fafa DC	25	Please describe what the rule should do:
eb39fafa DC	26
ebb53d86 TL	27
	28	What new ECMAScript feature does this rule relate to?
	29
	30	<!-- New rules must be related to ECMAScript features added within the last 12 months -->
	31
eb39fafa DC	32	What category of rule is this? (place an "X" next to just one item)
	33
	34	[ ] Warns about a potential error (problem)
	35	[ ] Suggests an alternate way of doing something (suggestion)
eb39fafa DC	36	[ ] Other (please specify:)
	37
	38	Provide 2-3 code examples that this rule will warn about:
	39
	40	<!-- Put your code examples here -->
	41	```js
	42
	43	```
	44
	45	Why should this rule be included in ESLint (instead of a plugin)?
	46
	47
	48	Are you willing to submit a pull request to implement this rule?