Separate into core and express packages
Nobody has claimed this yet.
- Dominant language
- F#
- Stars
- 860
- Forks
- 99
- Avg merge
- 22m
- Merged PRs (30d)
- 1
Description
Just as the python lib, Plotly.NET provides both low-level access to plotly.js figure generation (e.g.TraceStyle functions, Chart.Scatter) and high-level abstractions for composite charts (e.g. Chart.Grid, Chart.Range).
Once a full low-level coverage is reached on 2.x.x, it might be beneficial to split these layers to both make the chart namespace more concise and add dependencies such as a data frame library to the high level abstractions.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue does not name specific files or tests. Start by reviewing the project and package layout, then inspect the Chart namespace and the low-level TraceStyle and Chart.Scatter APIs alongside high-level Chart.Grid and Chart.Range abstractions. Done would require a defined split into core and express packages, but the required coverage and dependency boundaries still need clarification.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fsharp
- Domain
- developer-experience
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100