-
Notifications
You must be signed in to change notification settings - Fork 12
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
Convert DOM manipulation bans into a custom rule #123
Labels
Comments
Josehower
added
documentation
Improvements or additions to documentation
enhancement
New feature or request
labels
May 6, 2022
Handover Comment for the PR: What work has been done
What work is still open
who to take overThis Issue will be taken over either for @ProchaLu or @Eprince-hub Where to startThe best place to start would be checking the following issue in vs code: See if there is a new workaround found by the community. Other details that you know that are not captured already in the issue / PRIf at any point the issue microsoft/vscode#54272 is solved, this issue would be able to be solved right away. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Currently, we are using
no-restricted-syntax
config blocks to preventively banquerySelector
querySeletorAll
andgetElementById
. One of the issues with this is the warning messages don't allow us to add clickable links to the description of the error:One way to solve this Is moving these checks into a new custom ESLint rule:
eslint-config-upleveled/index.cjs
Lines 168 to 191 in 085d47f
The text was updated successfully, but these errors were encountered: