Closed cpsievert closed 5 months ago
- Can we provide typing/autocomplete on
render_func.widget
/render_func.value
?
We currently have support for render_func.value
, but not for render_func.widget
. To get render_func.widget
, we'd need to have special methods like @render_plotly
as the widget class is not provided by the user but could be provided by the renderer's typing.
I've added a commented render_plotly
method as a working prof-of-concept
- Deprecate register_widget()?
See #127 . This can be done in a followup PR
I am strongly against doing render_fn.value
or render_fn.widget
and have it call any reactivity.
py-shiny did not implement reactive values for clarity. I'm going to continue with that approach and make helper methods for reactive_read()
/ reactive_depend()
on the render_widget
class.
This PR helps solve the problem of needing a widget object in scope if you want to set/get attribute values, and thus, effectively eliminates any need for
register_widget()
TODO
render_func.widget
/render_func.value
?register_widget()
?Example/testing app