keystonejs/keystone-classic

TextArray field type causes client JS errors

Open

#4,412 建立於 2017年8月8日

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

描述

Expected behavior

  1. No JS error when item is selected from Select field.
  2. Additionally dependsOn working when set in TextArray field.

Actual/Current behavior

  1. Error thrown: Uncaught TypeError: nextProps.value.join is not a function whenever item is selected from a Select field.
  2. TextArray field does not appear when dependency met.

Steps to reproduce the actual/current behavior

TestList.add({
	selection: { type: Types.Select, initial: true, required: true, options: 'a,b,c' },
	items: { type: Types.TextArray, initial: true, dependsOn: { selection: 'b' } }
});

Environment

Software Version
Keystone 4.0.0-beta.5
Node 8.2.1

貢獻者指南

技術棧
javascriptreactnodejs
領域
frontendbackend
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Basic knowledge of Keystone field typesFamiliarity with React admin UI
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
60
研究方向
Investigate the TextArray field component and the Select field component in the Keystone admin UI. The error 'nextProps.value.join is not a function' suggests that nextProps.value is not an array. Check how the value is passed from the Select field to the TextArray field. Also, examine the dependsOn logic to ensure the TextArray field appears when dependency is met. Relevant files are likely in the fields directory, such as 'fields/types/TextArray.js' and 'fields/types/Select.js'.