keystonejs/keystone-classic

field of relation fields as default columns not working

Open

#4,593 建立於 2018年3月7日

在 GitHub 查看
 (1 留言) (0 反應) (0 負責人)JavaScript (14,656 star) (2,288 fork)batch import
bughelp wanted

描述

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

貢獻者指南

技術棧
javascriptnodejs
領域
backendfull stack
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
mostly clear
前置要求
KeystoneJS basic knowledgeNode.js environment
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
35
研究方向
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.