You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
getCurrentConnections is inconsistent across different Windows versions.
Current behavior
Currently it returns the key/value mixed up:
See the output of .getCurrentConnections():
The odd one to me is the one coming from win11. win10 makes more sense.
Windows 11:
Windows 10:
This is the output of netsh wlan show interfaces for each version:
Windows 11:
Windows 10:
Which are the affected features
node API
CLI
Which is your operating system?
Windows
Environment
Windows 11 and 10.
Version of node-wifi
2.0.16
Steps to Reproduce
See the output of netsh wlan show interfaces
See the output of .getCurrentConnections()
Solutions
Maybe parsing the results differently according to the OS.
I see there's a difference in the number of results for the netsh command so maybe that's the issue as it offsets the parsing.
The text was updated successfully, but these errors were encountered:
Expected behavior
getCurrentConnections
is inconsistent across different Windows versions.Current behavior
Currently it returns the key/value mixed up:
See the output of
.getCurrentConnections()
:The odd one to me is the one coming from win11. win10 makes more sense.
Windows 11:
Windows 10:
This is the output of
netsh wlan show interfaces
for each version:Windows 11:
Windows 10:
Which are the affected features
Which is your operating system?
Windows
Environment
Windows 11 and 10.
Version of node-wifi
2.0.16
Steps to Reproduce
See the output of
netsh wlan show interfaces
See the output of
.getCurrentConnections()
Solutions
Maybe parsing the results differently according to the OS.
I see there's a difference in the number of results for the
netsh
command so maybe that's the issue as it offsets the parsing.The text was updated successfully, but these errors were encountered: