On 26/08/2015 8:00 AM, Jombart, Thibaut wrote: > Hi there > > thanks for the answer. > >>> But are their better ways / best practices? >> You'll have to ask questions like these on a Shiny forum. > > Done. New thread there: https://goo.gl/17hsAa > >>> On a related topic: are there plans of formally incorporating shiny apps in >>> the structure of a R package, so that the checks will run through the code >>> of the apps as well? > >> No, but it would be very easy to do: just write a function that tests >> those things, and call it from a script in the tests directory. > > Yes, though in this case tests would merely check that the code can be > sourced without error. I was thinking more of looking for unstated > dependencies in code effectively used by the package, though indirectly. I > guess it is only relevant if distributing shiny apps alongisde packages > becomes common practice. I am not sure how trendy it is yet, but wouldn't be > surprised to see it become increasingly frequent.
Your test function can test whatever interests you. If you want to test for dependencies, just do it. You can see how R implements those tests by looking in the tools package, and either use them directly, or modify them to your needs. Duncan Murdoch ______________________________________________ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
