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

Lollipop chart

Open
#417 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Stale
Tech stack
fsharp

Research direction

Start in src/Plotly.NET/ChartAPI/Chart2D.fs by reading the existing Range chart and Chart.Bar implementations. Prototype in a scripting or notebook environment, using line charts connected from zero to each data point. Done means a top-level lollipop chart API with data input supporting #IConvertible, following the library's existing chart patterns.

Written by the indexing model from the issue text.

Description

Area: Core API Type: Enhancement
Description

A Lollipop chart is a categorical chart that is basically a bar chart replaced by points being connected by a line to the zero-line of the reference axis representing the data. It can be helpful to reduce visual noise when all values have a similar height [1].

Example:

Pointers
  • Ideally, you start prototyping in a scripting or notebook environment where you can iterate fast. installation instructions can be found here: https://plotly.net/#Installation
  • Charts like this that are using baseline trace types to create a new chart type should only be implemented in the top-level Chart API. An example where this is already done is the Range chart that combines a set of differently styled line charts.
  • When possible, use #IConvertible for data input, as this allows for strings, number types such as int and float, and DateTime.
References
Hints (click to expand if you need additional pointers)
  • The most suitable base chart for this is a set of line charts that each connect the zero line to a data point
  • The high-level function should look quite similar to the base implementation of Chart.Bar
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 Data Visualization issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.