-
Notifications
You must be signed in to change notification settings - Fork 325
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
Create a service locator for clients to be used in various locations #419
Comments
#433) * #419: Create a service locator for clients to be used in the commands. * #419: argh... tests... * Update env_profile.yaml remove unrelated .yaml change * Update env_profile.yaml made REDIS_PROFILE a string again, as travis fails on PHP 7.1 and 7.2 * rename method * follow test functions name convention.
Sorry for my late reply, I've been swamped in work so haven't had a chance really to look at this yet. Right now we're maintaining 2.x and 3.x is "coming some day". |
@curry684 I guess this one can be closed no? Should we add some docs about it? |
Nah think it's fine like this, I kept it open mainly as a reminder to look at it once we'd cleaned up for 3.x but given the overall direction I don't see a reason to keep it around. |
@curry684 Do you think we should document this feature or it should be marked as internal? |
As far as I'm concerned it's an implementation detail. If library consumers wish to use similar functionality they can and should use service subscribers instead. |
Makes sense, agree! Thx! |
#409 (comment)
Given that it's a change in
master
only we'll now have to ensure we have a service locator so the commands and other explicit usages still work.The text was updated successfully, but these errors were encountered: