Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Separate into core and express packages

Open
#209 0 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
fsharp

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.

Description

Area: Meta Type: Enhancement

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.

Dominant language
F#
Stars
860
Forks
99
Avg merge
22m
Merged PRs (30d)
1

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from plotly/Plotly.NET

All issues in plotly/Plotly.NET

Similar issues

More DevTools issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.