hasura / hasura/graphql-engine

Naming convention on client side

Open
#9,825 0 comments 0 reactions 0 assignees View on GitHub
k/enhancement
Dominant language
TypeScript
Stars
32.1k
Forks
3k
PR merge metrics
PR metrics pending

Description

### Is your proposal related to a problem?

Activating naming convention on server side introduce breaking for lib's tied to default conventions. Like https://github.com/hasura/ra-data-hasura

### Describe the solution you'd like

Allow client to choose naming convention on request by providing additional header like `X-Naming-Convention: `

Contributor guide

Open the contributing guide

Research direction

No file, test, or entry point is named. Start by tracing request handling and existing naming-convention configuration, then define how the proposed X-Naming-Convention header is validated and applied; done means clients can select a convention per request without breaking existing defaults.

Written by the indexing model from the issue text.

Assessment

Tech stack
graphql
Domain
api
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.