-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
Framework Integration #18466
Comments
Initially, when we were researching store/v2 we had a big push back for the Context upgrade. A pattern I proposed to avoid Context update was creating accessor functions. I started drafting it 2 years ago in this branch: |
Yeah, I can see that. @fdymylja tells me integration should be trivial w/ the new services/runtime stuff. Will be syncing with him shortly. But yes, I do want to avoid touching |
BTW, here is the "accessor pattern" draft: fc71bf4 |
Happening in parallel with server/v2 work. |
interfaces are aligned, we should be unblocked on this |
This issue is to mainly track the requirements needed in order to integrate store v2 into the wider SDK framework. I.e. replace store v1 usage with store v2 usage. This will most likely require rewiring of the
sdk.Context
type and perhaps other bits of refactoring.cc @tac0turtle
The text was updated successfully, but these errors were encountered: