Closed
Conversation
3 tasks
Member
|
Like in #4245, could we consider integrating These rules will not be respected if they're not enforced. |
Member
|
What needs to happen to revive this pull request? Or should we close and start anew? |
Member
|
Closing as stale without response. |
5 tasks
Member
|
I'd still like to see this at some point. I opened #15193 as a task issue after trying (and failing) to implement it again in the current codebase. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This PR replaces #4506 due to unresolvable merge conflicts
How has this been tested?
Running
npm run lint:jsdocin a terminal.Notes:
eslint/folder, although this is a temporary folder for ESLint configuration it wil suffice for the time being.Screenshots
Types of changes
JSDoc ESLint code linting
Checklist: