Releases: oegedijk/dash_oop_components
Releases · oegedijk/dash_oop_components
v0.0.8: component_callbacks and self.Input, self.Output
Version 0.0.8:
Breaking Changes
- component callbacks should now be declared in
def component_callbacks(self, app)
instead of_register_callbacks(self, app)
. Although for now the old_register_callbacks()
will still work.
New Features
- added .id(), .Input(), .Output() and .State() methods to DashComponent
- basically just tags
+'-'+self.name
to the end of acomponent_id
- results in somewhat cleaner callbacks:
html.Div(id=self.id("output-div") @app.callback( self.Output("output-div", "children"), self.Input("input-first-n", "value") ) def update_div(first_n): ...
- basically just tags
v0.0.6: tab-only querystrings, connectors, load from pickles
New Features
- If you add a parameter
filepath
to yourDashFigureFactory
you can.dump()
without specifying a filepath as it defaults to the filepath parameter.- If that
DashFigureFactory
is parameter for aDashComponent
(orDashApp
), you can
then load the pickled object instead of rebuilding theDashFigureFactory
from scratch.
This is useful for when you have a computationally expensive build process
for yourDashFigureFactory
. You can indicate that you would like
to try to load from pickles or only wish to load from pickles by
passingtry_pickles=True
orforce_pickles=True
when loading from config:
DashApp.from_yaml("dashboard.yaml", try_pickles=True)`
- If that
DashComponentTabs
: generate adcc.Tabs
wrapper with a list ofdcc.Tab
children based on a list ofDashComponent
subcomponents.DashConnector
: aConnector
can generate callbacks between
DashComponent
instances. This makes connections between components
also modular and re-usable.- Documentation here
Bug Fixes
- Cleaned up querystring code