novoda/merlin

String to Endpoint

Mecharyry opened this issue · 1 comments

Problem

A String representing an Endpoint is passed all the way down through Merlin. The type String makes it difficult to see all usages of what is meant to be an Endpoint and does not enforce type safety. In future, if we wanted to add any validation around this String we would need to extract an additional class or swap this out.

Potential Solution

Replace the String representation of an Endpoint with a concrete implementation of an Endpoint to enforce type safety.

Impact

We can accurately see all usages of Endpoint. Easy to add validation to Endpoint should we wish it in the future.

This has been addressed and will be released as part of v1.0.0.