keystonejs/keystone-classic

Multiple relationship display confusing

Open

#2,319 opened on Feb 23, 2016

View on GitHub
 (5 comments) (0 reactions) (0 assignees)JavaScript (14,656 stars) (2,288 forks)batch import
UXhelp wanted

Description

If I have a list that defines multiple relationships as follows:

MyList.relationship({ ref: 'RefList', path: 'listPath1', refPath: 'refPath1' });
MyList.relationship({ ref: 'RefList', path: 'listPath2', refPath: 'refPath2' });
MyList.relationship({ ref: 'RefList', path: 'listPath3', refPath: 'refPath3' });

then the Admin UI shows it like this:

Relationships

Ref List

No related Ref List

Ref List

No related Ref List

Ref List

Name        Foo       Bar
refPath1    foo1      bar1

No where is the path defined in the relationship definition used to distinguish the relationship listing, instead the referenced relationship name (ref) is used, which makes looking at the display confusing since it's hard to tell which is which.

Contributor guide

Tech stack
javascript
Domain
backendfrontend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Familiarity with KeystoneJS Admin UIKnowledge of relationship configuration
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Investigate the Admin UI template that renders relationships for a list. The issue indicates the relationship name (ref) is used as the heading instead of the path. Locate the template or component responsible for generating the relationship listing and modify it to use the path property as a distinct label. Check the issue comments for any additional context or suggestions.