Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move global variables to Services module #2025

Merged
merged 2 commits into from
Oct 21, 2015

Conversation

floehopper
Copy link
Contributor

User-visible changes

None

Motivation

The Services module was added relatively recently in commit 34f8f7f. This introduced a different way to "lookup" clients to external APIs. I'm not sure whether there's an official GDS way to do this, but this new way seems a bit better than using global variables. The main thing is that we should only do this one way which is what this PR addresses.

Technical details

Hopefully this is fairly obvious from the diffs.

@chrisroos chrisroos self-assigned this Oct 21, 2015
@chrisroos
Copy link
Contributor

Looks good to me.

@floehopper floehopper force-pushed the move-global-variables-to-services-module branch from efa1b46 to 13fc6a2 Compare October 21, 2015 16:55
@floehopper
Copy link
Contributor Author

I've rebased this against master and force-pushed in preparation for merging.

floehopper added a commit that referenced this pull request Oct 21, 2015
…ces-module

Move global variables to Services module
@floehopper floehopper merged commit d59d882 into master Oct 21, 2015
@floehopper floehopper deleted the move-global-variables-to-services-module branch October 21, 2015 17:01
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