Feature Request: Type errors on excess arguments

[madsbuch]

Hi!

First and foremost, thanks for at great library! We use it extensively to provide a TS-native experience when querying our graphQl backend.

We do have one issue though: It would be nice to see type errors when we try to supply and argument to a query and mutation that does not exists:

const resp = await graphQlClient('mutation')({
    createFormSubmission: [
    {
        nonExistingVar: "This should give a type error"
    }, { ... }
    ]
})

When refactoring, we rely on typescript to tell us where we forgot to make changes. This small update would give a huge value in this process.

[aexol]

In 5.4.0 it is better but arguments are still a challenge

[SimonKlausLudwig]

Would also appreciate that! The way I "fixed it" for me is to chain multiple Selectors. This works well:

chain('query')({
    getRunningMode: true,
    getState: Selector('State')({
        configureDisplay: Selector('ConfigureDisplay')({
            displayProfil: Selector('DisplayProfile')({
                width: true,
            })
        }),
        stationMainInformation: {
            departures: Selector('Departure')({
                destinationText: true
            })
        }
    })
});

The only problem im facing right now is that if I set "getRunningMode" to false, I want get an error when trying to access getRunningMode. What's the point to make it possible to set a value to false? If I don't want to query it, ill just leave it out.