Validate port is integer type for SocketPool #78
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.
While ESP32-SPI's socket validates if a user passes an invalid port value:
#76 found that native socketpool does not validate port data type before connecting. When entering the port # in the
secrets.py
file, it may be not clear to people thatport
requires an integer value while most other values within the file require a string value.This pull request mirrors ESP32SPI's
RuntimeError
thrown when using a string as a port number into this library: