plotly / plotly/dash

Provide Input Patch-Like Behavior

Open
#2,470 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

feature P3
Dominant language
Python
Stars
24.4k
Forks
2.3k
Avg merge
2d 7h
Merged PRs (30d)
13

Description

Is your feature request related to a problem? Please describe.
With the introduction of the Patch component for outputs, I was thinking that it would be pretty useful as well to be able to configure Patch-like features for inputs as well. Right now, if any key of the dcc.Graph figure attribute changes, then a callback would be triggered, and all of the associated data would be sent across the network.

Describe the solution you'd like
Instead, it might be nice if we could get a bit more granular in specifying the keys within a figure or store's data configuration. I.e. Fire this callback if the actual data coordinates of the figure changes, but don't fire the callback if the user changes the color of the title.

Describe alternatives you've considered
I'm not actually sure how you would go about checking which underlying key of an attribute fired in a callback with the current implementation of Dash. Perhaps some sort of Store component that holds the previous figure state?

(Not an urgent request - just a nice-to-have down the line as partial updates start to receive first-class treatment and Dash applications start to process larger data sets).

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

Start by reading the existing Patch component behavior alongside dcc.Graph input handling and callback triggering. Define how granular changes within figure or store data should affect callback execution and network transfer, then verify the behavior across the relevant input and callback flows.

Written by the indexing model from the issue text.

Assessment

Tech stack
python, react
Domain
api, frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.