Sgqlc does not throw an eror when a filter of an invalid field is given

[mike-sosa-sofarocean]

For example if we have a input

class DogInput(sgqlc.types.Input):
     __schema__ = wex_schema
    birth_date = sgqlc.types.Field(ZonedDateTime, graphql_name='birthDate')

and we run a query with given filter

[{expression: GREATER_THAN_OR_EQUAL_TO, value: {adoptionAge: 3}}]

Then instead of throwing an error since DogInput doesn't have an adoption_age field, sgqlc will simply send the query with filter input

[{expression: GREATER_THAN_OR_EQUAL_TO, value: {}}]

Is this the intended result? And if so, is there a way of turning on error logging/debugging. It would be nice to know that the filters that you are trying to apply aren't valid.

[barbieri]

It's due the origin where the fields are looked, instead of looking at the given object (with extra fields), I do look at the known fields in the actual type.

I'll see if I can change this, it's been some time since I wrote it, but I recall for input objects I tried to be "more relaxed" allowing both the Python and GraphQL naming, thus this "direction".

However I'm bit busy, may take a while to look at it :-(