Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Sign upStandard does not warn of adding properties to non-extensible objects. #1201
Comments
This comment has been minimized.
This comment has been minimized.
|
Is there an ESLint rule that would warn against that? |
This comment has been minimized.
This comment has been minimized.
|
I'm not sure if a new one would need to be written or if one already exists. |
This comment has been minimized.
This comment has been minimized.
|
After discussion in the ESLint gitter, it seems unlikely that such a rule will be added, so closing this issue. |
setpill
closed this
Sep 24, 2018
lock
bot
locked as resolved and limited conversation to collaborators
Dec 23, 2018
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
setpill commentedSep 19, 2018
What version of standard?
12.0.1What operating system, Node.js, and npm version?
OS: Ubuntu 18.04
Node.js: v8.12.0
npm: 6.4.1
Example code
What did you expect to happen?
Standardjs to warn me of the TypeError that running this code throws.
What actually happened?
Standardjs gives no warning and the code throws a TypeError.