Christophe Dervieux
Christophe Dervieux
After some searching time, I find that the `"!DEBUG "` line are replace by two calls to `debugme::debug()`. Exemple from https://github.com/RLesur/crrri/blob/de6fd8e9f0402bc0d57e8f46b5872fddf7a5d47b/R/chr_connect.R#L227 gets transform in ``` debugme::debug(paste0(debugme::debug("!DEBUG Trying to find "),...
This is a `debugme` issue. It happens with : * In debug strings where we want R code to be catched. * with function called several times in the package....
Can't reproduce on a dummy 📦 . only happens with crrri. I put this on hold for now.
Another hint: Here is how the code is transformed after loading the package (this is when DEBUGME is parsed and transformed) ```r function (host = "localhost", port = 9222, secure...
I think i'll work again on that with the new API and it could be a good way to add functional tests.
Related to #8 to try using EventEmitter class instead of websocket to fix this bug
Look also at new feature of private loop autorun https://github.com/rstudio/chromote/pull/24
Currently it does not work as expected on my end. If I use `load = "source"` in DESCRIPTION, or `roxygen2::roxygenise(load_code = "source")` I get warnings about the roxygen tags for...
What another great use case for the event emitter API! I'll post a new example soon hoping it will work ok!
> > > What another great use case for the event emitter API! I'll post a new example soon hoping it will work ok! OK for reference, I tested the...