This warning was happening to dependent packages on R CMD check.
The problem is due to delayedAssign; it appears this can't be used safely, at least not to define package-level symbols that contain S4 or reference class objects.
If you call this in a package's .R file:
`delayedAssign("hello", stop("boom"))`
but don't refer to "hello" anywhere, when you run R CMD check on a dependent package you'll see the error.
If the expression needs the methods package (like Context$new()), you'll get an error unless the dependent package itself depends on methods.
I always thought dots and colons were illegal in HTML ID attributes,
but I was wrong. They are legal and because they are commonly used
in identifier names in R, Shiny users often like to use them. Worse,
Shiny gave no warnings when using dots and only a pretty advanced
subset of functionality would NOT work when using dots, causing
everyone to think they were fully supported in Shiny.
This commit ought to bring reality in line with perception. It turns
out that jQuery has an escaping scheme in its queries that allow us
to support dots after all. As long as we are always careful to
surround IDs with $escape when putting them in a query, we'll be in
good shape.
Colons will probably still cause problems at the moment because we
use colons internally to separate input type from input name. But
we've never seen users try to use colon in IDs before, so we can
wait to fix it until that becomes a problem.
the cause:
normalize('foo', '/') => C:/foo
normalize('foo/', '/') => C:/foo/
under Windows. For unix, the trailing slash will always be removed in normalizePath()
- makeReactiveBinding: Turns a "regular" variable into a reactive.
No need to use reactiveValues() for simple reactivity.
- setAutoflush (not exported): Causes flushReact() to be called
each time something is executed at the R console top-level.
- options(shiny.suppressMissingContextError=TRUE): Prevents the
"Operation not allowed without an active reactive context" error
when attempting to read a reactive value or expression from the
console.
the tab content visibility needs to be the union of data-display-if and whether the tab is active (the currenty implementation makes it always visible when data-display-if evaluates to true)
