Skip to content
This repository has been archived by the owner on Nov 28, 2020. It is now read-only.

Implement proper endpoint parsing #5

Open
4 of 5 tasks
jean-airoldie opened this issue Apr 9, 2019 · 0 comments
Open
4 of 5 tasks

Implement proper endpoint parsing #5

jean-airoldie opened this issue Apr 9, 2019 · 0 comments
Labels
feature request A request for a new feature help wanted Extra attention is needed tracking issue A issue that tracks other issues

Comments

@jean-airoldie
Copy link
Owner

jean-airoldie commented Apr 9, 2019

This is a tracking issue around the proper implementation of Endpoint.

Currently Endpoint only parses the transport and stores the address into a string without parsing. This is meant to future-proof our socket methods until proper parsing is developed.

These are the sub-issues to must be closed:

@jean-airoldie jean-airoldie added bug Something isn't working help wanted Extra attention is needed tracking issue A issue that tracks other issues feature request A request for a new feature and removed bug Something isn't working labels Apr 9, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
feature request A request for a new feature help wanted Extra attention is needed tracking issue A issue that tracks other issues
Projects
None yet
Development

No branches or pull requests

1 participant