keystonejs/keystone-classic

field of relation fields as default columns not working

Open

Aperta il 7 mar 2018

Vedi su GitHub
 (1 commento) (0 reazioni) (0 assegnatari)JavaScript (14.656 star) (2288 fork)batch import
bughelp wanted

Descrizione

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

Guida contributor

Tech stack
javascriptnodejs
Dominio
backendfull stack
Tipo issue
bug
DifficoltàQuanto dovrebbe essere impegnativa per un nuovo contributor.
3
Tempo stimatoTempo stimato per completare e verificare uno scope piccolo.
1-3 hours
Stato attivitàQuanto è probabile che la issue sia ancora attiva e reviewable.
stale
ChiarezzaQuanto chiaramente la issue descrive problema, scope e risultato atteso.
mostly clear
Prerequisiti
KeystoneJS basic knowledgeNode.js environment
Adatta ai principiantiQuanto la issue è adatta a contributor alla prima esperienza.
35
Direzione di ricerca
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.