new_file_block | R Documentation |
Similarly to new_data_block()
, blocks created via new_file_block()
serve
as starting points in analysis pipelines by providing data to down-stream
blocks. They typically will not have data inputs and represent root nodes in
analysis graphs.
new_file_block(server, ui, class, ctor = sys.parent(), ...)
new_filebrowser_block(
file_path = character(),
volumes = c(home = path.expand("~")),
...
)
new_upload_block(...)
server |
A function returning |
ui |
A function with a single argument ( |
class |
Block subclass |
ctor |
String-valued constructor name or function/frame number (mostly for internal use or when defining constructors for virtual classes) |
... |
Forwarded to |
file_path |
File path |
volumes |
Parent namespace |
All blocks constructed via new_file_block()
inherit from
file_block
.
In order to make user data available to blockr, this block provides file-
upload functionality via shiny::fileInput()
. Given that data provided in
this way are only available for the life-time of the shiny session, exported
code is not self-contained and a script containing code from an upload block
is cannot be run in a new session. Also, serialization of upload blocks is
currently not allowed as the full data would have to be included during
serialization.
In order to make user data available to blockr, this block provides file-
upload functionality via shiny::fileInput()
. Given that data provided in
this way are only available for the life-time of the shiny session, exported
code is not self-contained and a script containing code from an upload block
is cannot be run in a new session. Also, serialization of upload blocks is
currently not allowed as the full data would have to be included during
serialization.
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.