Repository navigation
Tools for debugging components #16
Description
It's hard to know when/why a component is 'mis-specified'. Furthermore, my current debugging process is not ideal (app$layout_set(component); app$layout_get(); app$run_server()). Some ideas for improvements:
- Printing a component could spin up a simple dash app with just that component.
- Provide a 'debugging mode/option' where client side errors are listed in a pop-up (the current generic
Error loading dependenciesmessage is not helpful and most folks won't know to open their browser's dev tools) - Automatically type check arguments in R using the components
propTypesdefinition
Activity
cpsievert commentedon Dec 20, 2017
For (1), it'd be useful to print a "server-less" webpage -- is this possible @chriddyp? Have any examples?
chriddyp commentedon Jan 2, 2018
A lot of this will be
dash-rendererspecific. This is quite a bit of work, and I'm working on getting commercial sponsorship for this.rpkyle commentedon Aug 26, 2020
Quite a lot of work has been undertaken in
dash-renderervia the dev tools UI, and through the use ofPropTypes.js. This is now available to all Dash backends "for free", and any future work on improving debugging is likely to be handled within JavaScript. Closing as resolved.