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
Hi, could you please provide some kind of mechanism how to say guardrail to follow openApi specification when generating code from swagger? Specifically I am talking about query parameters with array type (but there could be more differences), which are handled as multi (userId=1,userId=2) insted of default comma separated values (userIds=1,2). According to specification if there is no
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.