the GraphQL schema is generated successfully, but using Type as a name for the type, mutation and queries. Since this could possibly lead to name clashes (a type could exist for e.g. addresses, projects, etc.) there should be the possibility to pass an additional parameter (e.g. --gqlname) to avoid this. That way e.g. --gqlname=AddressType could be passed and that would be used for replacement for the schema file.
Bonus: Detection if a gqlname is already in use and subsequent notification in the command line.
Added to the command --gqlName=NewGraphQLName can now be used to override the GraphQL schema file. However, it will revert to the ModelName if not used.
When using the following command
the GraphQL schema is generated successfully, but using Type as a name for the type, mutation and queries. Since this could possibly lead to name clashes (a type could exist for e.g. addresses, projects, etc.) there should be the possibility to pass an additional parameter (e.g. --gqlname) to avoid this. That way e.g. --gqlname=AddressType could be passed and that would be used for replacement for the schema file.
Bonus: Detection if a gqlname is already in use and subsequent notification in the command line.