hasura / hasura/graphql-engine
Custom tables names should be used when tracking relationships
- Dominant language
- TypeScript
- Stars
- 32.1k
- Forks
- 3k
- PR merge metrics
- PR metrics pending
Description
### Version Information
Server Version: 2.1.1
### Environment
OSS
### What is the expected behaviour?
Custom table names should be used when tracking (new) relationships.
### What is the current behaviour?
Custom table names are NOT suggested when tracking a new relationship. The original/underlying table name is used instead. This makes the "track all relationships" button completely useless to me.
### How to reproduce the issue?
1. Create tables `a` and `b`, with `b` having a foreign key to `a`
2. use custom names `my_a` and `my_b`
3. track relationships, the original names will be used instead of the custom names (but this can be edited)
4. clicking "track all" won't allow modifying the name
### Screenshots or Screencast
1. table definitions




2. table relationships (expecting my_bs and my_a)


3. schema relationships

Contributor guide
Research direction
Start from the “track all relationships” entry point and the relationship-tracking flow described in the reproduction steps. Reproduce the case with custom names `my_a` and `my_b`, then trace where suggested relationship names are generated from the underlying foreign-key tables. Done means both individual tracking and “track all” use the custom names.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100