Graeme Coupar

Handle recursive input objects

1

This function infinitely recurses if it finds an input object that contains itself: https://github.com/obmarg/cynic/blob/master/cynic-querygen/src/query_parsing/inputs.rs#L181-L211

This gives a kind of crap error just now, could easily be improved: ``` #[derive(cynic::InputObject)] #[cynic( graphql_type = "Query", schema_path = "tests/test-schema.graphql", )] struct BlogPost { Content: String, #[cynic(rename =...

I'm not entirely sure what's needed to do this, or in what ways it breaks. The first step of this issue will be to try and generate some code from...

#391 refactored the way variables work. I'm not 100% happy with the errors that you get if you use a variable that doesn't exist, or use an incorrect type. This...

I've documented rename/alias _slightly_ on the [`QueryFragments` page of the book](https://cynic-rs.dev/derives/query-fragments.html#field-attributes), but could go into a bit more detail about the use cases, how to use it to fetch multiple...

Better decoding errors

4

Decoding errors currently only include details of the field that failed, no info on where in the response that was. Might be nice to figure out how to improve them

We have (or at least used to have)[ some suggestion logic for when you accidentally typo a type name. Would be good to consolidate this as part of the `Schema::lookup`...

Currently it happens at query building time. For performance this may be sensible, but it means I have no way to propagate errors unless I change a lot of APIs...

I'm currently refactoring the internals of cynic pretty heavily to move logic out of the `use_schema` output and into `QueryFragment`. This issue is to track the progress of that work:...