elastic/kibana

Saved object import: show validation errors in UI

Open

#166,795 建立於 2023年9月20日

在 GitHub 查看
 (1 留言) (1 反應) (0 負責人)TypeScript (19,065 star) (8,021 fork)batch import
Feature:Saved Objects ManagementTeam:Coregood first issue

描述

If importing saved objects results in the API returning validation errors these errors should be displayed in the UI so users can take action on them.

For example, importing a dashboard with kibanaSavedObjectMeta.searchSourceJSON as a object instead of a string causes the API to respond with:

{
    "successCount": 0,
    "success": false,
    "warnings": [],
    "errors": [
        {
            "id": "elasticsearch-storage-dashboard",
            "type": "dashboard",
            "meta": {
                "title": "Cluster Ingest Per Day (Technical Preview/Beta)",
                "icon": "dashboardApp"
            },
            "error": {
                "isBoom": true,
                "isServer": false,
                "data": null,
                "output": {
                    "statusCode": 400,
                    "payload": {
                        "message": "[attributes.kibanaSavedObjectMeta.searchSourceJSON]: expected value of type [string] but got [Object]: Bad Request",
                        "statusCode": 400,
                        "error": "Bad Request"
                    },
                    "headers": {}
                },
                "type": "unknown"
            }
        }
    ]
}

But the UI just shows "Error" without any explanation

貢獻者指南

技術棧
typescriptreactnodejsrest api
領域
frontendbackend
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Familiarity with Kibana's saved object import flowReact knowledgeUnderstanding of API error response structure
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
70
研究方向
Investigate the UI component that handles saved object import results, likely in the saved objects management plugin. The API returns validation errors in a structured format as shown in the issue. The current UI displays a generic 'Error' message. The fix likely involves parsing the error response and displaying the specific error messages (e.g., from `error.output.payload.message`) in the import result flyout. Look at the import API client and the component that renders the import summary. Linked files: src/plugins/saved objects management/ or similar. No open PRs or assignees.