remove extraneous TCP/IPC properties from RedisOptions TS type #1707
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.
Node 18 introduced a new
keepAlive
option in the TCP socket constructor.This causes ioredis's TypeScript typings to clash with
@types/node
, because we definekeepAlive
asnumber | undefined
, whereas Node defines it as aboolean
.Luckily, this isn't a runtime regression. We don't pass
keepAlive
intocreateConnection
, and in fact only pass in three properties total. But we pretend that any property ofTcpNetConnectOptions
can be included inRedisOptions
.This PR reduces the surface-area of
RedisOptions
to only include the TCP and IPC connection parameters that we actually use, which results inkeepAlive
once again having the correct TS type.It should also be less confusing for users, as we've removed several unused properties off of that interface...
Fixes #1680
Fixes #1684