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
So it seems we should implement a repr_html.htmlwidget (and maybe repr_html.formattable? I haven't fully understand the knit_print.*() hierarchy/call chain in formattable yet) and also check that we have the same display mechanism as rstudio (do they have a way to deliver plots to the plot area?).
Regarding things we have no rich printing for: I've no clue how to reliably tell if we miss a repr_xxx.class_type (and tell the user that they should bug us or the package owner for such a method) or that the package author didn't want a visible output. If someone has a clue...
CC: @renkun-ken (owner of the formattable package)
The text was updated successfully, but these errors were encountered:
I think this happens when
print(f)
does not print anything and we don't have anything to make a rich display...In rstudio, the
f
already triggers something, so we really should implement the same way rstudio handles this...this also triggers a display in rstudio and sets x:
So it seems we should implement a
repr_html.htmlwidget
(and mayberepr_html.formattable
? I haven't fully understand theknit_print.*()
hierarchy/call chain in formattable yet) and also check that we have the same display mechanism as rstudio (do they have a way to deliver plots to the plot area?).Regarding things we have no rich printing for: I've no clue how to reliably tell if we miss a
repr_xxx.class_type
(and tell the user that they should bug us or the package owner for such a method) or that the package author didn't want a visible output. If someone has a clue...CC: @renkun-ken (owner of the formattable package)
The text was updated successfully, but these errors were encountered: