Simplify usage by supporting new Socket API without nullable loop arguments #419
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.
This changeset simplifies usage by supporting the new Socket API without nullable loop arguments.
Note that this doesn't affect the API of this package at all, but does use the improved API of the referenced Socket component. Existing code continues to work as is.
Together with #418, #417 and #410, this means we can now fully rely on the default loop and no longer need to skip any arguments with
null
values. Additionally, this now consistently uses theHttpServer
andSocketServer
class names to avoid class name collisions and ambiguities.Builds on top of reactphp/socket#264 and reactphp/socket#263