chore: reset info.serialNumber when resetting mock ports #1899
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.
BREAKING CHANGE
Resetting the value in the phony port's
info.serialNumber
propertywhen
BindingMock.reset()
is called will make its behavior "moredeterministic." This is useful when doing deep-equality checks against a
BindingMock
instance (or more specifically, aSerialPort
instancecontaining a
BindingMock
instance); judicious use ofBindingMock.reset()
will mean a developer can expect the value ofinfo.serialNumber
to be deterministic when tests are run in any orderor in isolation.
People have a tendency to code their way around stuff like this, so this
is potentially a breaking change for somebody somewhere.