Is it possible to specify a complexity limit that doesn't apply to schema introspection? Or to manually set the complexity cost for schema introspection?

I took a look through the generated code, but didn't see any hooks relating to this (I may very well have missed it).

One of the specific advantages of the wire approach is that it generates code that's relatively readable compared to reflect-based equivalents. When wire.Value is used on a small by-value type, there's no need for the value to live in a global variable - the expression could instead be used literally inside the generated code, which would make the code easier to follow, and more similar to the c

In:
https://github.com/TheDan64/inkwell/blob/f768691fccb04fe262a6ccf22c215657dc08de98/src/context.rs#L950
the lifetimes are left implicit, which unnecessarily shortens the lifetime of the return value. Making the lifetimes explicit:

impl<'ctx> Context<'ctx> {
    pub fn const_string<'a>(&'a self, string: &'a [u8], null_terminated: bool) -> VectorValue<'a> {
        ...
    }
}

We noticed that our api is failing with 404 error when the query string date field is not a full OffsetDate Sting format.
for example:
this request pass:
curl 'https://ai.twilio.com/v1/Transcripts?AfterDateCreated=2020-11-22T23:46:00Z' -u $AC:$TK
but this one fails:
curl 'https://ai.twilio.com/v1/Transcripts?AfterDateCreated=2020-11-22' -u $AC:$TK

the error we get in the internal service i

The Generated Client API is remains largely undocumented...

It would also be awesome if we could include the documentation of the API in the Generated DSL

As noted in #122, setting up AppSync debugging in a Carthage-based project is challenging. We need to provide some developer documentation around that workflow to make it easier for developers to debug AppSync if they suspect a problem with the SDK.

See the documentation of the config file format.

The current state of existing configs (click to expand).