plotly / plotly/plotly.R

New feature request: a modeBarButtonsToKeep argument in the config function

Open
#1,740 2 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

good-for-first-time-contribution help wanted
Dominant language
R
Stars
2.7k
Forks
641
PR merge metrics
No merged PRs in 30d

Description

Currently plotly has a function to remove listed mode bar buttons.

It'd be nice if it had a function to keep listed mode bar buttons, and to drop the rest.

Otherwise the code is quite long-winded if a user only wants to keep one button, such as the camera.

This argument could be called modeBarButtonsToKeep

library(dplyr)
library(ggplot2)

plot <- ggplot(iris) +
  geom_point(aes(Sepal.Width, Sepal.Length))

plotly::ggplotly(plot) %>% 
  plotly::config(modeBarButtonsToRemove = list("zoom2d", "pan2d", "zoomIn2d", "zoomOut2d", 
"autoScale2d","resetScale2d", "hoverClosestCartesian", "hoverCompareCartesian", 
"sendDataToCloud", "toggleHover", "resetViews", "toggleSpikelines", "resetViewMapbox", 
"toggleSpikelines", "resetViewMapbox", "lasso2d", "select2d"))

Contributor guide

Open the contributing guide

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.

Research direction

Search the repository for plotly::config and the existing modeBarButtonsToRemove handling. Trace how configuration reaches the mode bar, then verify that a modeBarButtonsToKeep argument preserves only the listed buttons; the issue does not name a file or test to run.

Written by the indexing model from the issue text.

Assessment

Tech stack
r
Domain
data-visualization
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.