You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 dependencies message 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 propTypes definition
The text was updated successfully, but these errors were encountered:
Quite a lot of work has been undertaken in dash-renderer via the dev tools UI, and through the use of PropTypes.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.
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:Error loading dependencies
message is not helpful and most folks won't know to open their browser's dev tools)propTypes
definitionThe text was updated successfully, but these errors were encountered: