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

fix: propagate graphql client to child clients #6851

Merged
merged 1 commit into from Mar 8, 2024

Commits on Mar 7, 2024

  1. fix: propagate graphql client to child clients

    This regressed in 62ced56, and meant
    that child clients were invalid, and couldn't be called with `Do()`, as
    well as causing `GraphQLClient()` to return an invalid nil value.
    
    This only previously worked because the GraphQL client and the dagger
    client shared the same name `client`. When this property was removed,
    the propagation stopped working. Now, we make this special case
    explicit.
    
    Signed-off-by: Justin Chadwell <me@jedevc.com>
    jedevc committed Mar 7, 2024
    Copy the full SHA
    4681454 View commit details
    Browse the repository at this point in the history