Publicly re-export "reqwest" to fix version mismatch in `post_graphql`

[nothingnesses]

Hi. I'm trying to use the post_graphql function with the "reqwest" feature enabled. Even though my project depends on both this library and "reqwest", I'm hitting the "two different versions of crate `reqwest`" error. As such, I can't construct a reqwest::Client that post_graphql accepts.

Suggested Solution

Could we add a re-export of the "reqwest" crate when the feature is enabled?

I.e, in "src/graphql_client/reqwest.rs":

#[cfg(feature = "reqwest")]
pub use reqwest_crate as reqwest;

This should allow downstream users to do the following:

// Use the exact version of reqwest that graphql_client expects.
use graphql_client::reqwest::{post_graphql, reqwest::Client};

// This should now work.
post_graphql(&Client::new() ...);

For now, I'm manually copying the function implementation into my project to bypass the type mismatch, but a re-export would be much cleaner and more user-friendly.

I'd be happy to implement this fix and make a PR myself, but let me know if there's a different approach you'd prefer, or if you think I'm missing something obvious that'd let me use post_graphql without relying on my work-around.

In any case, thanks for the library!

[magiccrafter]

Pinning to a version of reqwest lower than the one specified by graphql_client in your app causes you to lose access to new features, security patches, performance improvements, and more.

By accepting &reqwest::Client directly, graphql_client made their internal dependency you problem :)
A better design would be to abstract over the client.

[tomhoule]

I think a good solution would be having multiple reqwest features (reqwest_0_14, reqwest_0_15, etc.) for different versions of reqwest, as in other crates. Maybe we can do this for graphql-client 0.16.

[magiccrafter]

I agree that multiple reqwest features will be a great addition but what about the maintainability. As an open source project this may be an overkill for the maintainers. The simplest way forward is to just keep all the dependencies up-to-date and force clients to upgrade. With the help of AI coding agents it is getting easier to keep up with upgrades.

Today the project is already in a good shape to abstract the client from the http libs like reqwest. That's what I did and works quite well.