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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is no test covering the
emitCurrentState: truepath inonStateChange, and in particular no test verifying that when the internal state fetch rejects, the promise rejection is swallowed and does not propagate (the core behavior this fix adds). The existing test at line 106 only exercises theemitCurrentState: false(default) code path. Given that the rest ofBleManager.jsis thoroughly covered and the whole purpose of this PR is to prevent an unhandled rejection, a test ensuring this behavior works correctly (e.g. mockingBleModule.stateto reject and asserting no unhandled rejection is thrown) would be valuable.