keystonejs/keystone-classic

field of relation fields as default columns not working

Open

#4593 opened on Mar 7, 2018

View on GitHub
 (1 comment) (0 reactions) (0 assignees)JavaScript (14,656 stars) (2,288 forks)batch import
bughelp wanted

Description

Expected behavior

with below model

B { bValue: { type: String} }

A { b: { type: Types.Relationship, ref: 'B', many: false } } A.defaultColumns ='b:bValue';

With above setting, in admin ui, the 0.3 version is showing b:bValue in the A list. but with 4.beta this is not working.

Actual/Current behavior

Steps to reproduce the actual/current behavior

Environment

Software Version
Keystone 4 beta8
Node 6.12.0

Contributor guide

Tech stack
javascriptnodejs
Domain
backendfull stack
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
KeystoneJS basic knowledgeNode.js environment
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
35
Research direction
Investigate the KeystoneJS admin UI code, specifically how default columns for relationship fields are resolved. Review the change from version 0.3 to 4.beta8 that broke the 'b:bValue' syntax. Look at the List module's defaultColumns parsing logic and the field component rendering in the admin UI. The issue reporter provided a clear model example, so replicating the setup and debugging the column resolution would help identify the regression.