Fix legacyMode/pingInterval issue #2386
Merged
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.
Description
Fixes #2383 - when
pingInterval
is used with a client inlegacyMode
an error was thrown (see #2383) - this PR aims to resolve the issue.Checklist
npm test
pass with this change (including linting)?I do not have Docker installed under WSL, so am unable to run your test suite. I was hoping CI might take care of this. You don't seem to have a
npm run format
or similar command to apply autofixes to the formatting and I cannot run the test suite without Docker, so cannot confirm if linting passes.Is a documentation update included (if this change modifies existing APIs, or introduces new ones)?