* Add onTestSnapshot function
* Add shiny.testing option
* Add entry to staticdocs index
* Bump version to 0.14.1.9002 and update NEWS
* Document params for onTestSnapshot
* Add session$enableTestEndpoint() method
* Un-export applyInputHandlers
* Grunt
* Provide inputs, outputs, and snapshot at test endpoint
* Remove non-working example
* Fix var name in documentation
* Rename shiny.testing to shiny.testmode
* Rename onTestSnapshot to exportTestValues and add example
* Add session$getTestEndpointUrl
* Grunt
* Add module support to exportTestValues
* Test endpoint allows specifying specific values
* session$getTestEndpointUrl: add arguments for choosing which values to return
Squashed commit of the following:
commit bdc4080032ff6b5b2de0f799aa307272f3905003
Author: Dean Attali <daattali@gmail.com>
Date: Mon Oct 17 18:18:03 2016 -0700
add PR link to news item
commit 22c695cde2b270ba8ec37d4862ad1f30de76ce68
Author: Dean Attali <daattali@gmail.com>
Date: Mon Oct 17 15:01:24 2016 -0700
update NEWS for #1422 fix
commit e669548c13f84f0929e4131c641a8333e08baa26
Author: Dean Attali <daattali@gmail.com>
Date: Sat Oct 15 12:45:49 2016 -0700
allow shiny.trace option to specify which type of messages to relay; fixes#1422
It is dangerous to set this on a per-process basis. If we even
still want the ability to have observer errors not kill the
session (debatable) we should do so by having an option on the
session object that is set when the shiny server function runs.
Not only does this remove support for the option, but now we
will refuse to connect and will abort the session if the option
is set to a non-NULL value. This is to prevent apps from moving
forward with the assumption that their option will work, when
it really won't. (I doubt anyone is using it anyway, it's so
obscure...)
