Add IServiceProvider to public GraphService ctors

[brianjackson71]

Due to a change in the inventorySetQuantities mutation in version 2026-04, I need to pass a null value for changeFromQuantity. Which means I need a way of changing the serialisation options to not ignore null valued properties.

Looking at the implementation of GraphService, is method InitializeDependences which takes an IServiceProvider parameter. In theory I could register alternative json settings object in DI and GraphService would use it.

Unfortunately, all of the public ctors pass a null IServiceProvider to InitializeDependences.

I propose a nullable IServiceProvider parameter is added to all public GraphService ctors which is then passed to the InitializeDependences call in these ctors.

This appears to be a safe change and I'm happy to raise a PR for it, but thought I'd discuss it here first.

[nozzlegear]

Hey, thanks for asking about this! Right now my intent with the IServiceProvider constructors is to keep them internal for those individual service classes[†], and then use the *ServiceFactory classes to pass in the IServiceProvider when we need to override it. So I think you should be able to do this:

var services = new ServiceCollection();
services.AddSingleton(new JsonSerializerOptions
{
    NumberHandling = JsonNumberHandling.AllowReadingFromString,
    Converters = { new JsonStringEnumConverter() },
    PropertyNamingPolicy = JsonNamingPolicy.CamelCase,
    // Always send null-valued properties
    DefaultIgnoreCondition = DefaultIgnoreCondition.Never
});

var serviceProvider = services.BuildServiceProvider();
var factory = new GraphServiceFactory(serviceProvider);
var graphService = factory.Create("example.myshopify.com", "your-access-token");

Try that and let me know if it works for you? If not I'm happy to consider opening up those constructors!

[†] They should probably be made protected, actually, so inheritors can use the same constructor.

P.S. I've been meaning to draft a new release for 2026-04 as soon as I have some free time, let me know if you run into any other blockers with it.

[brianjackson71]

Thanks for the advice. It mostly works, put doesn't entirely fit.

The company I work for operate several Shopify stores, when moving to a new api version, we update them individually (one or two to test the waters, then a few more and finally the rest).

Using the factory, as suggested, I couldn't find a way of supplying the api version when calling the Create method.

From what I can see, that would involve changes to the factory and GraphService (and/or my initial proposed changes).

P.S. I've not encounter any other issues targeting 2026-04. I'm not sure how you can support the inventorySetQuantities mutation changes without breaking earlier versions.