@timelyportfolio LOL (2 years later almost related to your comment on shinyNextUI) I am facing the case where I have nested tags. Do you have an example of how to use hydrate from reactR. I am not very sure to what to pass to a component parameter (hydrate(component, tag)):
My use case is the following, using phosphoricons:
str(phosphoricons::ph_i("house"))
List of 3
$ name : chr "i"
$ attribs :List of 1
..$ class: chr "ph-light ph-house ph-lg"
$ children:List of 1
..$ :List of 10
.. ..$ name : chr "phosphor-icons"
.. ..$ version : chr "1.4.1"
.. ..$ src :List of 1
.. .. ..$ file: chr "assets"
.. ..$ meta : NULL
.. ..$ script : NULL
.. ..$ stylesheet: chr "css/icons.min.css"
.. ..$ head : NULL
.. ..$ attachment: NULL
.. ..$ package : chr "phosphoricons"
.. ..$ all_files : logi TRUE
.. ..- attr(*, "class")= chr "html_dependency"
- attr(*, "class")= chr "shiny.tag"
- attr(*, "browsable_html")= logi TRUE
Contrary to shiny::icon, the later also adds the dependency to the icon in the children, which causes some issues. I can solve it by removing the dependency from the shiny tag and add it separately but if we could use hydrate that would be better.
I am not even sure that would be a solution, since the dependency would also have to be injected in the page head.
Thanks :)
@timelyportfolio LOL (2 years later almost related to your comment on shinyNextUI) I am facing the case where I have nested tags. Do you have an example of how to use
hydratefrom reactR. I am not very sure to what to pass to a component parameter (hydrate(component, tag)):My use case is the following, using
phosphoricons:Contrary to shiny::icon, the later also adds the dependency to the icon in the
children, which causes some issues. I can solve it by removing the dependency from the shiny tag and add it separately but if we could use hydrate that would be better.I am not even sure that would be a solution, since the dependency would also have to be injected in the page
head.Thanks :)