Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for callback timing and general graph improvements #223

Closed
rpkyle opened this issue Aug 13, 2020 · 1 comment · Fixed by #224
Closed

Support for callback timing and general graph improvements #223

rpkyle opened this issue Aug 13, 2020 · 1 comment · Fixed by #224
Assignees
Labels
feature parity Modifications to improve parity across Dash implementations size: 3
Milestone

Comments

@rpkyle
Copy link
Contributor

rpkyle commented Aug 13, 2020

We should lay the foundations for supporting the features added by plotly/dash#1179 as a follow-up to plotly/dash#1176, which will permit timing of callback execution and add the ability to reorganize existing nodes on the graph when the dev tools UI is opened (among other improvements):

image

The changes required are relatively trivial and could be added concurrently with the upcoming pattern matching callbacks PR for our next CRAN release.

@rpkyle rpkyle linked a pull request Aug 15, 2020 that will close this issue
1 task
@rpkyle rpkyle added the size: 3 label Aug 15, 2020
@rpkyle rpkyle self-assigned this Aug 15, 2020
@Marc-Andre-Rivet Marc-Andre-Rivet added feature parity Modifications to improve parity across Dash implementations labels Aug 18, 2020
@Marc-Andre-Rivet Marc-Andre-Rivet added this to the R & Julia milestone Aug 18, 2020
@rpkyle
Copy link
Contributor Author

rpkyle commented Oct 30, 2020

This was added in #235 via #224. Closing!

@rpkyle rpkyle closed this as completed Oct 30, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature parity Modifications to improve parity across Dash implementations size: 3
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants