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

Export plot objects as plotly Figures

Open
#1 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
45/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Stale
Tech stack
plotly, python

Research direction

Start in mozaic/plotting.py around lines 18-40, where the plotting steps culminate in the Plotly Express show() call. Preserve the existing data munging and aesthetic options while exposing the generated plot object for later customization. Done means callers can adjust items such as date ranges, titles, legends, or annotations instead of only rendering immediately.

Written by the indexing model from the issue text.

Description

This may be a simpler one, but the current plotting code includes multiple steps:

  1. Some helpful data munging
  2. Some aesthetic design options for the plots
  3. A call to plotly express show() the ultimately generated plot here: https://github.com/mozilla/mozaic-forecasting/blob/2becad6a9b372c8f0d732f91ee92f6b8d7b06fed/mozaic/plotting.py#L18C1-L40

By either just removing this fig.show() call, or setting up a different function call that outputs the plot object, it will still automatically render in most typical Jupyter/iPython/Notebook contexts. But it will have the benefit of being customizable after-the-fact, which the current approach is not--at least not without extensive workarounds.

Example: Wanting to manually specify the x-axis date range of the plot, or change the title/legends, or add an annotation region.

Dominant language
Python
Stars
3
Forks
3
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 mozilla/mozaic-forecasting

All issues in mozilla/mozaic-forecasting

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.