Generating name and description fields for queries and mutations as per the naming guidelines

[severussundar]

Naming Guidelines

We assume that the entity name defined by the user will be singular. Users have the option to provide singular and plural names for the entities through the config. When singular and plural names are provided, the queries and mutations will be generated with these specified names. When they are not specified, the entity name will be used for generating the query and mutation fields in the schema. The _by_pk and list queries will be generated with first letter in lowercase as a best practice.

What is the Change?

The following fields were changed to follow the naming guidelines.

• Name and description for _by_pk query field.

• Name and description for the query to fetch all items

• Description for mutations

How was this tested?

• Unit tests

• Updating the config files with singular plural definitions and checking the schema

• Entity Stocks has the following graphQL definition in the config file.

"Stocks": { "source": "stocks", "rest": true, "graphql": { "type": { "singular": "Stock", "plural": "Stocks" } }

• Queries:

• Mutations:

[aaronpowell]

Are we potentially breaking the naming expectations that a person has from their database?

If we have a table named People we're saying that you're going to have to refer to the entity as Person in the schema for singlar operations (mutation deletePerson not mutation deletePeople), which means that we're really overriding their naming design.

Is that a level of opinionation that we're happy to have in the runtime?

[seantleonard]

Thanks for bringing to finish line. A few comments/nits about checks on tests for pluralize being not null.

[Aniruddh25]

LGTM! Thanks for pushing through this and validating the various scenarios.