Queries do not include __typename

[eettaa]

Before opening, please confirm:

• I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
• I have searched for duplicate or closed issues.
• I have read the guide for submitting bug reports.
• I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
• I have removed any sensitive information from my code snippets and submission.

How did you install the Amplify CLI?

No response

If applicable, what version of Node.js are you using?

No response

Amplify CLI Version

n/a

What operating system are you using?

n/a

Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.

n/a

Amplify Categories

api

Amplify Commands

codegen

Describe the bug

aws-amplify/amplify-codegen#445 has hung in pending triage for nearly four months without response but is actively blocking TS development. Reopening this bug as a plea for process review/friendly nudging of the relevant people on the aws side to actually please take a look at that bug.

Expected behavior

(literal): codegen'ed queries include __typename
(meta): there is some way to actually prod for updates on bugs (and/or explicit communication that they will not be addressed, but that to me would be a reason to move off of Amplify).

Not trying to be harsh- please let me know if I can help with a fix/help in any way to resolve this problem!

Reproduction steps

aws-amplify/amplify-codegen#445

GraphQL schema(s)

# Put schemas below this line

Project Identifier

No response

Log output

# Put your logs below this line

Additional information

No response

[josefaidt]

Hey @eettaa 👋 thanks for raising this and apologies for the delay on the codegen issue! I've marked this as a duplicate feature request of #445 and have bumped this with the team 🙂

[eettaa]

Just checking here- it was marked as duplicate of aws-amplify/amplify-codegen#445, right? the link in your comment points to a different bug...

Thanks!

[arsene-riaworx]

any update on this? Indeed #445 is a different bug!

[dhallX]

having same issue any update?

[josefaidt]

Hey folks apologies for the confusion, and great callout! Yes, this is a duplicate of the codegen issue aws-amplify/amplify-codegen#445, not #445 here in this repository.

[eettaa]

Thanks @josefaidt for your response... any chance there's an update on the real bug as well? (aws-amplify/amplify-codegen#445)

[AnilMaktala]

Hey @eettaa, This issue has been resolved in the latest version. Hence, closing this issue.

[github-actions]

This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.