Murat Tasan

Ah, I see now that the `do.call()` dispatching to `glue::glue()` already _can_ pass along additional named args (e.g. `.transformer`), but perhaps it'd make sense to set options like these as...

So the first issue I've run into is that I'm not sure how to easily _remove_ (or deregister) Loggers from the global index once created. It appears that dropping the...

Minor change to deal with the sometimes-explicit-sometimes-implicit root logger: ```R ## vectorized remove_logger

This single issue is perhaps the biggest blocker to me adopting {box} more thoroughly. I wind up resorting back to `library()` with the _intention_ of replacing those statements with more-carefully...

> in general, if a user runs box::use(foo[bar]) followed by box::use(foo[baz]), they want both of the names (bar and baz) to be attached, rather than the second expression superseding the...

I think (ii) is the natural and preferred behavior, yes. I only mentioned (i) in case you wanted to preserve backwards-compatibility, since _technically_ it'd be a change from the current...

@jcheng5 oh that's an interesting idea that I hadn't considered. You're right that it'd be a bit awkward to specify the use of the value as a function, but if...

I experimented a bit with the input handler returning a function and figured I'd share my thoughts. The naïve implementation looks something like so: ```R registerInputHandler("my.custom.InputBinding", function(data, ...) { function()...

UPDATE: I realized this isn't specific to magrittr or pipelines; here's a third output that also displays the err (when `input$row_ix` is `NULL`): ```R output$text_3

@daattali there's the `Shiny.shinyapp.isConnected()` function ... does that work for your use case? Either way, I also struggle with this, e.g. when trying to send a message to the server...