Closed ericleb010 closed 3 years ago
Typing for TcpSocket.address() seems to be different from what the library returns at runtime.
Steps to reproduce the behavior:
Or code:
// Your code
Calling TcpSocket.address() returns an object that resembles: {family: 'IPv4', port: 54014, address: '192.168.200.143'}
TcpSocket.address()
{family: 'IPv4', port: 54014, address: '192.168.200.143'}
According to the type definitions, TcpSocket.address() should just be a string: '192.168.200.143'
'192.168.200.143'
Screenshots If applicable, add screenshots to help explain your problem.
@ericleb010, you are right! Thanks for the feedback, working on a fix.
:tada: This issue has been resolved in version 5.0.0 :tada:
The release is available on:
Your semantic-release bot :package::rocket:
Description
Typing for TcpSocket.address() seems to be different from what the library returns at runtime.
Steps to reproduce
Steps to reproduce the behavior:
Or code:
Current behavior
Calling
TcpSocket.address()
returns an object that resembles:{family: 'IPv4', port: 54014, address: '192.168.200.143'}
Expected behavior
According to the type definitions,
TcpSocket.address()
should just be a string:'192.168.200.143'
Screenshots If applicable, add screenshots to help explain your problem.
Relevant information