Nicolas Dickinson

So I can see that #11 is a challenge fundamentally. But perhaps first education of package developers to follow patterns that will help us differentiate conditions. For this one, you...

So after having a think and looking at the code, I think the easiest for the end user would be to have a way to configure existing and new conditions...

Not to mention, the option to decide if any condition should be muffled like this: https://github.com/r-lib/rlang/issues/482 and https://rlang.r-lib.org/reference/cnd_muffle.html

I liked the second workaround for immediate application but it appears, futile.logger is no longer maintained since 2016: https://github.com/MazamaScience/MazamaCoreUtils/issues/54 Perhaps best to switch to this one: https://github.com/daroczig/logger I tried the...

I think this is also related to #70

Ok now also seeing this #62 where you have a positive list of signal conditions (and better understanding the overall function!). I think this option could also be managed in...

Wow, yes, a new release would be good but since I work across posix and windows, I think the current issue may be a show stopper. What do you think...

Ok great, the stateless approach can be very flexible. A global config file could be an R script/function with a series of short calls as proposed. A simple structured config...

@aryoda I've not seen changes in the remote feature branch. Let me know if there is some way I can help out (testing, code/PR, etc.)

Hi @aryoda, apologies for not picking this up sooner. I'm going to test this out now. Let me know if there is anything I should take into account (changes /...