hasura / hasura/graphql-engine

Default names shown in the field customization UI is wrong

Open
#9,287 1 comment 0 reactions 0 assignees View on GitHub
k/bug
Dominant language
TypeScript
Stars
32.1k
Forks
3k
PR merge metrics
PR metrics pending

Description

### Version Information

Server Version: 2.16.0 (and previous versions)

### Environment

Any

### What is the current behaviour?

Default names shown in the field customization UI is wrong in different cases.

#### Case 1 (when naming conventions are **not** enabled)

Generated field names are:

Screenshot 2022-12-12 at 12 02 30 PM

But default values shown in the UI are:

Screenshot 2022-12-12 at 12 04 02 PM

The default values are wrong for update_users_by_pk, delete_users_by_pk and update_users_many.

#### Case 2 (when naming conventions are enabled and set to graphql-default)

Generated fields are in camel case but the default values shown are in snake case:

Screenshot 2022-12-12 at 11 40 32 AM

### What is the expected behaviour?

#### For Case 1

Screenshot 2022-12-12 at 12 08 27 PM

#### For Case 2

Screenshot 2022-12-12 at 11 47 05 AM

### Keywords

field customization, custom graphql root fields

Contributor guide

Open the contributing guide

Research direction

Start by locating the field customization UI and the code that generates its default field names. Compare the displayed defaults with generated names for naming conventions disabled and graphql-default cases, including update_users_by_pk, delete_users_by_pk, and update_users_many. Done means the UI defaults match the generated fields in both cases and the behavior is covered by the relevant tests, if present.

Written by the indexing model from the issue text.

Assessment

Tech stack
graphql, typescript
Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.