-
-
Notifications
You must be signed in to change notification settings - Fork 4.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Change Request: Create new page for adding core rules #16648
Labels
accepted
There is consensus among the team that this change meets the criteria for inclusion
archived due to age
This issue has been archived; please open a new issue for any further discussion
documentation
Relates to ESLint's documentation
Comments
bpmutter
added
core
Relates to ESLint's core APIs and features
enhancement
This change enhances an existing feature of ESLint
triage
An ESLint team member will look at this issue soon
labels
Dec 11, 2022
mdjermanovic
added
documentation
Relates to ESLint's documentation
accepted
There is consensus among the team that this change meets the criteria for inclusion
and removed
enhancement
This change enhances an existing feature of ESLint
triage
An ESLint team member will look at this issue soon
core
Relates to ESLint's core APIs and features
labels
Dec 11, 2022
1 task
bpmutter
added a commit
to bpmutter/eslint
that referenced
this issue
Jan 19, 2023
Resolves eslint#16648
bpmutter
added a commit
to bpmutter/eslint
that referenced
this issue
Jan 21, 2023
Resolves eslint#16648
bpmutter
added a commit
to bpmutter/eslint
that referenced
this issue
Jan 28, 2023
Resolves eslint#16648
mdjermanovic
added a commit
that referenced
this issue
Feb 9, 2023
* docs: split rule docs Resolves #16648 * Add todo * add page to IA * Copy edits + remove TODO * Update docs/src/contribute/contribute-core-rule.md Co-authored-by: Nitin Kumar <[email protected]> * Apply suggestions from code review Co-authored-by: Nicholas C. Zakas <[email protected]> Co-authored-by: Milos Djermanovic <[email protected]> * Apply suggestions from code review Co-authored-by: Milos Djermanovic <[email protected]> * move rule performance testing to custom rules * Apply suggestions from code review Co-authored-by: Nicholas C. Zakas <[email protected]> Co-authored-by: Milos Djermanovic <[email protected]> * add basic custom rule overview --------- Co-authored-by: Nitin Kumar <[email protected]> Co-authored-by: Nicholas C. Zakas <[email protected]> Co-authored-by: Milos Djermanovic <[email protected]>
eslint-github-bot
bot
added
the
archived due to age
This issue has been archived; please open a new issue for any further discussion
label
Aug 9, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
accepted
There is consensus among the team that this change meets the criteria for inclusion
archived due to age
This issue has been archived; please open a new issue for any further discussion
documentation
Relates to ESLint's documentation
ESLint version
latest
What problem do you want to solve?
From eslint/rfcs#97 (comment):
The content of this page covers both custom rules and core (built-in) rules. Writing a custom rule and a core rule is basically the same. The page also includes some conventions we're using in core rules. I'm not sure where in the new hierarchy this page should be, and what its title should be, as it is of interest to both Extenders and Community Contributors.
What do you think is the correct solution?
From eslint/rfcs#97 (comment):
Participation
Additional comments
No response
The text was updated successfully, but these errors were encountered: