Clean up shiny and DT namespace

[schloerke]

Next version of shiny (1.4.0) is not (re)exporting the same functions as shiny v1.3.2. By importing shiny as a package, rather than all of the methods individually, it allows us a little bit of freedom to change the exported api.

We are planning on releasing to CRAN here shortly. If this change could be posted to CRAN soon, that would be great! (If not, please let us know. 😃 )

Thank you for your help!
- Shiny Team

---

My interpretation was the shiny methods were imported individually to avoid a namespace conflict with DT. It appears that DT is only used for its two methods, so the package can be namespaced on the function call directly.

[coveralls]

Coverage remained the same at 43.383% when pulling 35cab39 on schloerke:shiny-dt-namespace into 037e87d on sdcTools:master.

[bernhard-da]

hi @schloerke thx for the pr which i merge. the reason for explicitly importing all the shiny functions was because importing the entire package led to some conflicting warnings (in some old versions) that I can't reproduce any longer now :)

we'll probably add some little updates to the package and upload a new version to CRAN soon.

[schloerke]

Thank you!

---

Today I also learned (r-lib/roxygen2#617 (comment) ) about using raw namespace to avoid the conflict. This keeps it in line with the idea of "black listing" known conflicts, but importing everything else.

#' @rawNamespace import(shiny, except=c(dataTableOutput, renderDataTable))

[bernhard-da]

@schloerke that's really great information! thx

[schloerke]

@bernhard-da shiny will be heading to CRAN today. Without this change on CRAN, your package will not be able to install with the latest version of shiny. Thank you for your help!