plotly / plotly/Plotly.NET

[C#] Plotly.NET.CSharp Roadmap

未關閉
#379 0 則留言 3 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 Issue。

Area: CSharp Area: Meta Area: MissingAbstraction Type: Enhancement
主要語言
F#
星號
860
分支
99
平均合併
22 分鐘
30 天內合併 PR
1

描述

This issue tracks the roadmap for the native C# package Plotly.NET.CSharp

Plans on how to design and develop the C# API have been laid out and tracked in #285 and #322.

The general roadmap implementation-wise is the following:

  • 1. C# bindings for the high-level Chart construction API (#296), one binding per chart at first (no overloads)
  • 2. C# GenericChart Extension methods (this covers more or less all styling functions). Once these are finished, the F# extension methods for fluent interface can be removed.
  • 3. C# bindings for Object abstractions (TraceObjects, LayoutObjects, etc.) this might be a bit tricky
    Progress on this side has been made on the 'csharp-object-bindings' branch. In short, all these bindings can be auto-generated by using reflection on the F# objects. Might be worth to look into C# source generators

The way to go for the future is clearly code generation. The F# core API could in theory also created from the plotly.js JSON schema, but has many features that would be hard to automate such as type safety for enums etc.

To prevent having to namually maintain 2 code bases though, we should at least try to auto-generate the C# API based on the F# API, over which we have full control.

貢獻指南

這個儲存庫沒有索引到貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

研究方向

先閱讀路線圖項目以及 #285 和 #322 中先前的設計討論。檢查 csharp-object-bindings 分支,特別是 src/Plotly.NET.Codegen,並評估所提出的程式碼產生方式;當剩餘的 C# 擴充功能與物件繫結都已實作,且不需要手動維護第二套 API 時,路線圖即告完成。

由索引模型根據 Issue 內容生成。

評估

技術堆疊
csharp, fsharp
領域
tooling
Issue 類型
功能
難度
5/5
預估耗時
一週以上
活躍度
停滯
描述清晰度
需要釐清
新手友好度
25/100

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。