Changes to database selection - Saving connections
維護者通常 1 天內回覆
還沒有人認領這個 Issue。
評估
- 難度
- 5/5
- 預估耗時
- 一週以上
- 新手友好度
- 25/100
研究方向
先檢視 plugin 目前如何在圖表上儲存資料庫認證資訊，接著追蹤 migration 與 import/export 路徑。然後檢查圖表的資料庫選取 UI 與 WordPress 管理選單結構。當連線成為獨立且可重複使用的實體、現有圖表完成 migration、import/export 維持相容，且使用者可以如描述管理與選取連線時，即表示完成。
由索引模型根據 Issue 內容生成。
描述
Moved from https://github.com/Codeinwp/visualizer-pro/issues/248
Context: Multiple users want to be able to re-use old connections instead of having to retype the details. We want to give them an option to re-use an older connection for that purpose.
I also thought of the scenario, if a connection has a password change, at the moment users need to modify every chart to update the change. Making connections their own entity (that can be modified one and have the changes reflected on all charts that selected it) would make sense.
Here are the changes involved for this:
1- Creation of 'database connections'
Currently the credentials are tied to a specific chart, we want to separate the chart from the connection so they become separate entities.
Connections would then be stored separately from the chart, and charts would have a "connection_id" linking to the connection.
2- Migration
Existing credentials would have to be migrated to the new format, meaning for each chart with a connection to an external database, a connection record would be created with an automated name ex : "MySQL001, MySQL002" etc. and the charts would link to it with the corresponding ID.
3- Import/Export
We have to ensure import/export will work with the new structure.
4- Manage Connections page
In the menu, between "Add new chart" and "support, we would have a "Manage Connections" page
This page would be a standard WP crud page (like feedzy's https://i.imgur.com/uBFwOop.png) and allow users to modify all details of the connection, including the name (unique) and credentials. The modification would happen on a separate page (that we can link to later). Upon submitting modifications, a confirmation message will appear: "Are you sure you want to modify this connection? This will affect all charts linked to this connection".
It would also allow creating and deleting a connection, but would not allow deleting a connection linked to a chart.
We could also display a list of charts that use this connection and upon clicking on the chart name in the last, it could open it in edit mode.
5- Update the UI to select a database
Currently we have this: https://i.imgur.com/q6DIkOt.png
Changes:
- Reword the header to "Select a database connection"
- Remove the accordion (we want to make it more obvious that the user has more options)
- Upon selecting an option that is not Wordpress DB, a second dropdown will appear containing "New Connection" as well as all existing connections for this database type.
If the user chooses an existing connection, no other fields need to be displayed. We can have a button on the right of it that says "View/Edit this connection" which would open the edit page in a new tab.
If the user chooses "New Connection", it will be same as this: https://i.imgur.com/PS0O9rQ.png
Except there will be the "New Connection" dropdown and the connection name.
The connection will be created/saved when the user saves the chart itself, if the name was left empty, it will have a generic unique name (ex: MySQL001)
- 主要語言
- PHP
- 星號
- 108
- 分支
- 29
- 平均合併
- 1 天 5 小時
- 30 天內合併 PR
- 8
環境準備
- 沒有 Dockerfile 或 Docker Compose 檔案
- 有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
Codeinwp/visualizer 的其他 Issue
-
feature-request-triage
難度 4/5 3-5 天 新手友好度 64/100
Codeinwp/visualizer#1388 ·
維護者通常 1 天內回覆
-
`visualizer_schedule_refresh_db` remains missing after Visualizer reactivation可能已有人在做 @Alexia-Soare 於 6 天前認領。 未關閉bug-report bug-report-triage customer report
難度 4/5 3-5 天 新手友好度 48/100
Codeinwp/visualizer#1384 · 4 則留言 · 已指派 1 人 ·
維護者通常 1 天內回覆
-
Action Scheduler queue cleanup fatals with "Unidentified action" after concurrent deletion可能已有人在做 @Alexia-Soare 於 10 天前認領。 未關閉bug-report bug-report-triage
Codeinwp/visualizer#1369 · 已指派 1 人 ·
維護者通常 1 天內回覆
-
Action Scheduler async queue crashes on WordPress 5.3 with `wpdb::db_server_info()` error可能重新可做 @girishpanchal30 於 46 天前認領，目前沒有進行中的 PR。 未關閉bug-report bug-report-triage crash-report
Codeinwp/visualizer#1361 · 5 則留言 · 已指派 1 人 ·
維護者通常 1 天內回覆
-
Add a Default value for font settings可能重新可做 關聯的 PR 已關閉且未合併。 未關閉
難度 2/5 1-3 小時 新手友好度 25/100
Codeinwp/visualizer#1111 ·
維護者通常 1 天內回覆
查看 Codeinwp/visualizer 的全部 Issue
相似的 Issue
-
難度 2/5 1-3 小時 新手友好度 65/100
521xueweihan/HelloGitHub#3790 ·
-
bug
難度 2/5 1-3 小時 新手友好度 88/100
維護者通常 1 天內回覆
-
enhancement
難度 2/5 1-3 小時 新手友好度 68/100
-
難度 2/5 1-3 小時 新手友好度 78/100
benjaminkott/bootstrap_package#1670 ·
-
sync-en
難度 2/5 1-3 小時 新手友好度 85/100
維護者通常 2 天內回覆