add --statement-max-depth flag to optional parameters

[chrisbonifacio]

Description of changes:

Related GitHub issue #, if available:

Instructions

If this PR should not be merged upon approval for any reason, please submit as a DRAFT

Which product(s) are affected by this PR (if applicable)?

• amplify-cli
• amplify-ui
• amplify-studio
• amplify-hosting
• amplify-libraries

Which platform(s) are affected by this PR (if applicable)?

• JS
• Swift
• Android
• Flutter
• React Native

Please add the product(s)/platform(s) affected to the PR title

Checks

• Does this PR conform to the styleguide?

• Does this PR include filetypes other than markdown or images? Please add or update unit tests accordingly.

• Are any files being deleted with this PR? If so, have the needed redirects been created?

• Are all links in MDX files using the MDX link syntax rather than HTML link syntax?
  
  ref: MDX: [link](https://docs.amplify.aws/)
  HTML: <a href="https://docs.amplify.aws/">link</a>

When this PR is ready to merge, please check the box below

• Ready to merge

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[josefaidt]

is this a valid CLI option? I'm not seeing it in the help, but if it is we should get it added to the help

ampx generate graphql-client-code

Generates graphql API code

Stack identifier
  --stack  A stack name that contains an Amplify backend                [string]

Project identifier
  --app-id  The Amplify App ID of the project                           [string]
  --branch  A git branch of the Amplify project                         [string]

Options:
  --debug             Print debug logs to the console [boolean] [default: false]
  --help              Show help                                        [boolean]
  --profile           An AWS profile name.                              [string]
  --out               A path to directory where config is written. If not provid
                      ed defaults to current process working directory. [string]
  --format            The format that the GraphQL client code should be generate
                      d in.
              [string] [choices: "modelgen", "graphql-codegen", "introspection"]
  --model-target      The modelgen export target. Only applies when the `--forma
                      t` parameter is set to `modelgen`
         [string] [choices: "java", "swift", "javascript", "typescript", "dart"]
  --statement-target  The graphql-codegen statement export target. Only applies
                      when the `--format` parameter is set to `graphql-codegen`
    [string] [choices: "javascript", "graphql", "flow", "typescript", "angular"]
  --type-target       The optional graphql-codegen type export target. Only appl
                      ies when the `--format` parameter is set to `graphql-codeg
                      en`
  [string] [choices: "json", "swift", "typescript", "flow", "scala", "flow-moder
                                                                  n", "angular"]
  --all               Show hidden options                              [boolean]

[chrisbonifacio]

It is and we should!

[josefaidt]

would you mind filing a quick bug report for this in the backend repo? are there any other options we should add?

(in the future I'd like to generate this page from the CLI itself)

[chrisbonifacio]

Done! aws-amplify/amplify-backend#1546

Not aware of other missing options, scanned through the amplify-backend codebase and found where the commands are listed. Some are missing but are explicitly set to be hidden.

https://github.com/aws-amplify/amplify-backend/blob/4e7d59fb8226830e0c58dc48b2efd28d56254470/packages/cli/src/commands/generate/graphql-client-code/generate_graphql_client_code_command.ts#L207