hasura / hasura/graphql-engine
console: allow custom names for foreign keys and uniq keys
- Dominant language
- TypeScript
- Stars
- 32.1k
- Forks
- 3k
- PR merge metrics
- PR metrics pending
Description
the console should allow setting a custom name for foreign keys and uniq keys during creation and also allow editing name of existing constraints. By default we can keep the name field as optional
### Discussed in https://github.com/hasura/graphql-engine/discussions/7414
Originally posted by **nizamani** August 19, 2021
Hi Hasura Team,
We are using Hasura CLI, we make changes locally and then they are deployed to cloud through github. Question I want to ask is this. Is there is any way we can rename foreign key constraints to custom names? Just like check constraints we have name them with any custom names we like it would be nice if we can do the same for foreign keys. Right now Hasura assigns name to foreign keys automatically and I don't see an option in Hasura cli console to name foreign keys.
Contributor guide
Research direction
Start by locating the console flows for creating and editing foreign-key and unique constraints, then read the linked discussion for the intended behavior. Done means the console accepts optional custom names during creation and supports renaming existing constraints.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgres, typescript
- Domain
- databases, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100