You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We're using sgqlc to interact with a GQL service we've built and love the removal of dict-of-stuff navigation in the response objects and field selections. We can't quite figure out how to do the same for complex argument/input values though.
As an example:
Which as the schema grows become increasingly unwieldy. Is there a way that we are missing to do this or is there a way to generate classes that will act in this way using introspection of the sgqlc’s autogenerated classes?
The text was updated successfully, but these errors were encountered:
I focused on the read-side of the data, it's basically implemented by the sgqlc.operation and selectors, so I think the creation side will need some specific work to allow that.
Shouldn't be hard as input types are much simpler and particularly if you stick with __init__ and __setattr__ to set values.
I did this for some other project (customer private), not hard... but takes some time I don't have at this moment. This month is being particularly busy at work. I'll try to get back to sqglc development in June.
We're using sgqlc to interact with a GQL service we've built and love the removal of dict-of-stuff navigation in the response objects and field selections. We can't quite figure out how to do the same for complex argument/input values though.
As an example:
Ideally we would be able to generate a filter by:
This would benefit from tool tips and autocomplete where as the current method we're aware of is:
Which as the schema grows become increasingly unwieldy. Is there a way that we are missing to do this or is there a way to generate classes that will act in this way using introspection of the sgqlc’s autogenerated classes?
The text was updated successfully, but these errors were encountered: