feat: ignore camelcase rule for __webpack variables #530
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.
Motivation:
__webpack_nonce__
will always violate the camelcase rule.The error is usually ignored with
// eslint-disable-next-line camelcase
.It sounds reasonable to me to add the ignore rule by default.
An alternative approach could be to define
__webpack_nonce__
as globals. The advantage is that also the un-def violation is gone and globals are by default excluded from the camelcase rule. But it's weird to define__webpack_nonce
as global for every app using eslint when the variable is only available when bundled with webpack.