This repository was archived by the owner on Aug 29, 2025. It is now read-only.
Support Dash-Renderer 2.0 - *Breaking Changes*#128
Closed
Conversation
Member
Author
|
Prerelease versions are available with this code |
Contributor
|
@chriddyp Do we still want to keep this PR open, with regards to the new plan for 1.0 plotly/dash#469, and seeing as this is almost a year old? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR updates the components to support the features introduced in plotly/dash-renderer#32.
Namely, it will enable various properties across various components to accept arbitrary dash components as values.
For example, the
labelproperty indcc.RadioItemswill be able to take a arbitrary Dash component instead of just a string.i.e., instead of this:
the developer could do this:
This would require a dependency upgrade of
dash-rendererto a 2.0 series, which would cause other component libraries that are not compatible with that version to break. There should be no breaking changes within this library.This PR is a work-in-progress.