@maxerbubba I was looking for clarification in the exact code you ran to get the error. As far as I can tell your code seems to be a more reduced version of code sent to the sign method is it possible to send a more detailed code snippet as sending just the code you sent with the two objects results in an error due to missing information, or some more detail in exactly what you would like implemented. Also could you provide some clarification on the second possible solutionthrow "attribute `body` found in Signer, but `data` is missing. Please use attribute `body`" on what you would like implemented for this solution to work.

Whoops, I meant to put "data". (I edited the message above)

throw "attribute `body` found in Signer, but `data` is missing. Please use attribute `data`"

I was frustrated. This is just a convenience, to compare to similar libraries. I was initially using fetch(), and then was trying to switch to AmplifyJS signer, and my old code still had body.

• For example, fetch() uses body attribute https://developer.mozilla.org/en-US/docs/Web/API/fetch
• requests uses data attribute
• curl linux command uses --data attribute
• Amplify uses: data attribute https://aws-amplify.github.io/amplify-js/api/classes/signer.html

Adding a little type checking on the input object would be nice for developers to find bugs faster.

@maxerbubba So, if I understand correctly, you want to ensure that a body sent in the request object will be treated the same as sending data. Or you want an error thrown when there is a body in the request object but not a data attribute. Is there a preference between the two, or am I not getting what you want correct?

Closing this as it has been fixed by #10137

Thank you, @amehi0index ! 🚀