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

Should container binds be async? #10

Open
bradcypert opened this issue Feb 12, 2022 · 0 comments
Open

Should container binds be async? #10

bradcypert opened this issue Feb 12, 2022 · 0 comments
Labels
App Affecting or involving Steward's Application layer. Container Affecting or involving Steward's Containner layer. question Further information is requested

Comments

@bradcypert
Copy link
Contributor

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.

@bradcypert 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
App Affecting or involving Steward's Application layer. Container Affecting or involving Steward's Containner layer. question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant