This repository was archived by the owner on Jun 3, 2024. It is now read-only.
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.
Gives the following components persistence support (see plotly/dash#903):
Checklist
,DatePickerRange
,DatePickerSingle
,Dropdown
,Input
,RadioItems
,RangeSlider
,Slider
,Tabs
,Textarea
All but the date pickers persist only
value
.DatePickerRange
is the only one that persists more than one prop (start_date
andend_date
). We could imagine building a facility into persistence to omitpersisted_props
in this case, since it's pretty much useless to the user... for now I just mentioned this in the docstring.These components do not have persistence support:
ConfirmDialog[Provider]
,Graph
,Interval
,Link
,Loading
,Location
,LogoutButton
,Markdown
,Store
,Tab
,Upload
I think this is all straightforward, the only one I think might at some point want to get persistence support is
Graph
(selections, perhaps zoom or camera angle?), but this is not going to be simple to add, so I suggest omitting this until there's a clear need.