Proper way to omit non required query arguments?

[petersanchez]

Hi all. We recently updated from 0.17.29 to 0.17.49 and a query of ours broke.

Basically we have this:

input AdminBillingInput {
    orgSlug: String
    interval: Int
    dateStart: String
    dateEnd: String
}

type Query {
    getAdminBillingStats(input: AdminBillingInput): AdminBillingStats! @admin
}

A simple query that worked in 0.17.29:

query GetAdminBillingStats() {
            getAdminBillingStats(input: {}) {
                activeSubscriptions
                pendingCancelSubscriptions
                canceledSubscription
            }
        }

Now produces this error in 0.17.49:

gqlclient: HTTP server error (422 Unprocessable Entity): gqlclient: server failure: expected at least one definition, found )

I noticed this PR #2585 that adds omittable fields and am wondering if I need to use this new method for this query to run as it did before? I did try it quickly but got the same error. I tried setting nullable_input_omittable: true and generating the schema but it produces all sorts of code errors now because of the new type being passed into the resolvers.

I feel like I'm missing something obvious so just figured I'd ask to see what the best way is to run a query with an empty argument.

Thanks in advance!

[petersanchez]

OK, the issue was the parens in the operation name, that's why the various ways of the resolver name wasn't working. This query is working as expected.

query GetAdminBillingStats {
            getAdminBillingStats {
                activeSubscriptions
                pendingCancelSubscriptions
                canceledSubscription
            }
        }