chore: add ESLint rule to check if unsigned flag is necessary or not
#6325
Conversation
This file contains 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
AlCalzone
force-pushed
the
eslint-unsigned
branch
from
828b730 to
a24da65
Compare
|
@zwave-js-bot automerge |
zwave-js-bot
approved these changes
Sep 28, 2023
AlCalzone
added a commit
that referenced
this pull request
Sep 29, 2023
### Bugfixes * Ignore when a node reports `Security S0/S2 CC` to have version 0 (unsupported) although it is using that CC (#6333) ### Config file changes * Add Shelly to manufacturers (#6339) * Add Shelly Wave 1, Wave 2PM, update Wave 1PM association labels (#6326) * Add Sunricher SR-ZV2833PAC (#6310) ### Changes under the hood * Added an ESLint rule to help with deciding whether a config parameter needs to be `unsigned` or not (#6325, #6338)
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.
No description provided.