-
Notifications
You must be signed in to change notification settings - Fork 1
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
Proper use of rendering loaded components from the IO container #6
Comments
It does not cause an app a considerable amount of overhead, right? This is regarding the injection of the App instance. |
No, compared to the use of |
How about the injection of the App instance? Negligible overhead? |
Won't it be much better to inject $app instead of using this library? |
Elaborate. You're just asking questions without context
Yes you can, this library might serve as a reference instead. |
As the title proposed, we were left blinded out that we should resolve a new instance of class that is already present in the IO container, in fact, provided in the API. The
$app
variable is already inherited in which we can just call$app['instance']
instead of making a new one. A patch will be provided.The text was updated successfully, but these errors were encountered: