Amplify 10.6.1 breaks schema.graphql comment syntax

[eettaa]

How did you install the Amplify CLI?

npm

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

14

Amplify CLI Version

10.6.1

What operating system are you using?

Linux

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

Nope

Describe the bug

Prior to Amplify 10.6.x, schema.graphql comments were allowed to be inline
e.g., this was valid:

  idField: ID! # @index(name: "someIndexName", queryField: "queryFieldName")

... obviously, the comment was ignored/no index was created.

In Amplify 10.6.x, this now causes failures when you run any of the following:
amplify api gql-compile
amplfiy mock api
amplify push

The error is
🛑 Syntax Error: mismatched brackets found in the schema. Unexpected ) at line <number> in the schema.

Expected behavior

Comment semantics are not changed.

Reproduction steps

Create a toy schema
Add in the field I have provided above
Note that gql-compile fails.

Project Identifier

No response

Log output

# Put your logs below this line

Additional information

No response

Before submitting, please confirm:

• 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.

[biller-aivy]

+1

[josefaidt]

Hey @eettaa 👋 thanks for raising this! This appears to be a duplicate of #1143, can you confirm whether this accurately describes the issue you're experiencing?

[eettaa]

Yes, this is consistent. Sorry for missing the duplicate, apparently my search wasn't thorough enough. I'll keep an eye on that bug

[josefaidt]

Hey no worries @eettaa ! I'll mark this one as a duplicate in favor of tracking the existing item. Please subscribe to #1143 for further updates, however I believe this will be fixed with CLI 10.6.2

[AnilMaktala]

Hey @eettaa, Upgrading the CLI version to Amplify CLI v10.6.2 should resolve this issue.

[eettaa]

Hi @AnilMaktala thanks for this.
I look forward to upgrading to 10.6.2 one day but am currently stuck at 10.4 because of #1014 ... any chance that could get some attention as well, please?