keystonejs/keystone-classic

`select` on Types.CloudinaryImage doesn't do anything

Open

#4,560 建立於 2018年1月31日

在 GitHub 查看
 (0 留言) (0 反應) (0 負責人)JavaScript (14,656 star) (2,288 fork)batch import
4.x candidatebughelp wantedneeds reproduction

描述

Expected behavior

According to the documentation I can make the user select an existing CloudinaryImage: http://keystonejs.com/docs/database/#fieldtypes-cloudinaryimage

Actual/Current behavior

This is inside my model:

  image: {
    type: Types.CloudinaryImage,
    autoCleanup: true,
    select: true,
    folder: 'users',
    selectPrefix: 'users',
  },

using it with or without folder and selectPrefix, nothing happens to my UI. It's just the normal "Upload image" button.

Steps to reproduce the actual/current behavior

Add select: true to type: Types.CloudinaryImage

Environment

Software Version
Keystone 4.0.0-beta.5 & 4.0.0-beta.8
Node 8.9.4

貢獻者指南

技術棧
javascriptnodejsexpress
領域
backend
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
mostly clear
前置要求
無
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
40
研究方向
The issue reports that the `select` option on `Types.CloudinaryImage` does not work as documented. The bug is likely in the Cloudinary field type implementation. Start by locating the CloudinaryImage field definition in the Keystone source code (fields/types/cloudinaryimage). Check how the `select` option is handled in the field's UI rendering logic. Compare with other field types that support `select` (e.g., Types.Select) to understand the expected behavior. The documentation reference suggests that `select: true` should enable a UI to select existing images from Cloudinary. The issue may be missing a route or controller to fetch images from Cloudinary. Look for any recent changes or related issues in the repo (note: the issue is from 2018).