Skip to content

Conversation

@rposborne
Copy link

Previously two disperate objects could be passed into utils, a Gateway
or a Provider. This changes the signature to always expect a Gateway
It reduces the potential impact of this change from causing a double
lookup by lazy loading utils.

There are most likely additional refactors that are required here but
this allows the utils class not swallow unrelated errors.

Russell Osborne added 2 commits January 30, 2018 16:22
Previously two disperate objects could be passed into utils, a `Gateway`
or a `provider`.  This changes the signature to always expect a `gateway`
It reduces the potential impact of this change from causing a double
lookup by lazy loading utils.

There are most likely additional refactors that are required here but
this allows the utils class not swallow unrelated errors.
@rposborne
Copy link
Author

rposborne commented Feb 7, 2018

Both of the errors in style, and the failing spec are unrelated. The spec is failing as this rescue was rescuing things it shouldn't have.

@damianlegawiec damianlegawiec self-assigned this Nov 12, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants