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

Revert injector type hint to Injector #6945

Merged

Conversation

tractorcow
Copy link
Contributor

Fixes issues across the framework where Injector::inst()-create() doesn't resolve to anything.

@sminnee
Copy link
Member

sminnee commented May 22, 2017

Yeah — I guess this is is an important point: SilverStripe expects more than a PSR-11 object in place in order to function. It's both a DI container (get) and a generic factory (create).

@tractorcow
Copy link
Contributor Author

What suddenly is going on with travis?

image

@sminnee
Copy link
Member

sminnee commented May 22, 2017

Simon E added that, check recently merged PRs

@tractorcow
Copy link
Contributor Author

Oh no, what have I done. I may revert that PR. I should have inspected the output in more detail.

@tractorcow
Copy link
Contributor Author

tractorcow commented May 22, 2017

#6950 to fix

@sminnee
Copy link
Member

sminnee commented May 22, 2017

You don't like the more verbose output, then?

@tractorcow
Copy link
Contributor Author

I would if it were print on error only lol

@sminnee
Copy link
Member

sminnee commented May 22, 2017

Or at least error-or-slow. I wonder if it can be configured?

@tractorcow
Copy link
Contributor Author

According to @Firesphere there is an open issue to get that resolved, but it's not yet possible.

@tractorcow
Copy link
Contributor Author

See ScriptFUSION/Pip#5

@sminnee sminnee merged commit 29f450b into silverstripe:master May 24, 2017
@tractorcow tractorcow deleted the pulls/4.0/injector-typehint branch May 24, 2017 23:31
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