[C#] Plotly.NET.CSharp Roadmap
还没有人认领这个 Issue。
- 主要语言
- 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.
贡献指南
这个仓库没有索引到贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
调研方向
先阅读路线图条目以及 #285 和 #322 中之前的设计讨论。检查 csharp-object-bindings 分支,尤其是 src/Plotly.NET.Codegen,并评估所提出的代码生成方案;当剩余的 C# 扩展和对象绑定都已实现,且无需手动维护第二套 API 时,路线图即告完成。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- csharp, fsharp
- 领域
- tooling
- Issue 类型
- 功能
- 难度
- 5/5
- 预计耗时
- 一周以上
- 活跃度
- 停滞
- 描述清晰度
- 需要澄清
- 新手友好度
- 25/100