You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
bradcypert opened this issue
Feb 12, 2022
· 0 comments
Labels
AppAffecting or involving Steward's Application layer.ContainerAffecting or involving Steward's Containner layer.questionFurther information is requested
When binding data to a container, should we support async binds? If so, do we wait for all binds to resolve successfully before marking the container as ready to be used?
The alternative is that people would need to resolve their async items outside of the binding of the container and pass the result in to the binding function. I'm going down this path right now with a project and we'll see how it shapes out, but it felt weird at first.
The text was updated successfully, but these errors were encountered:
bradcypert
added
App
Affecting or involving Steward's Application layer.
Container
Affecting or involving Steward's Containner layer.
question
Further information is requested
labels
Feb 12, 2022
AppAffecting or involving Steward's Application layer.ContainerAffecting or involving Steward's Containner layer.questionFurther information is requested
When binding data to a container, should we support async binds? If so, do we wait for all binds to resolve successfully before marking the container as ready to be used?
The alternative is that people would need to resolve their async items outside of the binding of the container and pass the result in to the binding function. I'm going down this path right now with a project and we'll see how it shapes out, but it felt weird at first.
The text was updated successfully, but these errors were encountered: