hasura / hasura/graphql-engine
Better cues for naming convention override in source vs. global config
Open
k/enhancement
t/product-design
- Dominant language
- TypeScript
- Stars
- 32.1k
- Forks
- 3k
- PR merge metrics
- PR metrics pending
Description
Product enhancements to provide better cues to users for the naming convention config precedence specified in the green box at the end of this section: https://hasura.io/docs/latest/schema/postgres/naming-convention/#pg-source-naming-convention
Contributor guide
Research direction
Start with the naming convention documentation section linked in the issue, especially the green-box explanation of source versus global configuration precedence. Identify the specific user cues expected for that precedence; the work is done when users can understand which configuration takes priority without relying on unstated context.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgres
- Domain
- documentation
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100