-
Notifications
You must be signed in to change notification settings - Fork 535
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
DataObject: Deprecate Container Services #3799
Comments
Per discussion at October milestone planning, I'm moving un-projected issues out to Next. This should get picked up in a Refactor effort in the near future. |
Was about to create an issue to start this conversation, good timing. I believe the last time I talked with Vlad he told me that we can't switch over to the provider pattern just yet because the current pattern expects injections from the scope level only and there's more work required before we can migrate. Can we get clarity on this and the timeline here? :) |
@leeviana , Coming in later here but I don't fully get your question. Seems like Justin has taken point on starting the Providers integration. Is there something clearly blocking here? |
I just talked with justin and noticed that the "scope" object dependency Vlad was talking about really is just for getting the dependency global but any level can register things. Based on the code I saw, I believe we're unblocked, hopeful for some good progress here soon! :D |
This issue has been automatically marked as stale because it has had no activity for 180 days. It will be closed if no further activity occurs within 8 days of this comment. Thank you for your contributions to Fluid Framework! |
The
ContainerServices
code in Aqueduct that is no longer being consumed and has been replaced by the Providers pattern.This code needs to be removed.
The text was updated successfully, but these errors were encountered: