chore: use property shorthand to satisfy standard linter #50
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.
Summary
This PR makes a small, behavior-preserving style change to
index.jsto satisfy the Standard JS linter (object-shorthand). No functional changes were made.Motivation
The
standardlinter reported multipleobject-shorthandwarnings inindex.js(e.g.address: address,device: device,port: port). These are stylistic and can be safely rewritten using ES shorthand property syntax.Changes
address,device,portin two locations that build interface objects.keyin theWinregconstructor options object.Files changed
index.js(small, local-only formatting/idiomatic changes)Verification / How I tested locally
Run the project tests and linter in the repo root:
npm testExpected / observed results locally:
Example test output (local):
``
TAP version 13
spoof.normalize()
ok 1 should be strictly equal
ok 2 should be strictly equal
ok 3 should be strictly equal
spoof.random
ok 4 returns valid, normalized mac addresses
1..4
tests 4
pass 4
ok