Rory Finnegan
Rory Finnegan
Currently, the handler behaviour is split between handlers (e.g., DefaultHandler, CloudWatchLogs) and custom IO types (e.g., FileRoller, Syslogs.jl). This is largely a hold over from the Lumberjack.jl days. I think...
I think this will be related to #93, but I'm not sure if we want this for 1.0.
Would it make sense for `@test_nolog` to take a vector of pairs for each `level => regex`?
Looks like base does something closer to the pairs interface, but with tuples. ``` If we also wanted to test the debug messages, these need to be enabled with the...
Alright, looks like the base implementation is pretty hacky, so I'll just go with `@test_nolog ` for now.
Hmmm, that's pretty close to what already happens internally. I'm not sure how much I like the accessing of nested fields, but I wonder if we could break this up...
The alternative would likely result in noisy tests.
> Any reason why you required specifying the second argument when you added this function (at #261)? Because `cov2cor` is currently just a minimal copying version [`Statistics.cov2cor!`](https://github.com/JuliaLang/julia/blob/master/stdlib/Statistics/src/Statistics.jl#L513). We should probably...
I don't think Tables.jl is the right place for it. Maybe we should just have a TablePlots.jl package similar to how we have TableOperations.jl?
I don't think creating a custom IDE is the right solution here as that would be a much larger project to maintain. I also don't see a lot of benefit...