« first day (1748 days earlier)   

Duga
Duga
12:01 AM
RELOAD!
[rubberduck-vba/Rubberduck] 3 commits. 2 opened issues. 6 issue comments. 335 additions. 5 deletions.
[Zomis/minesweeper-flags-client] 1 commit. 35 additions. 1 deletion.
Minesweeper: Games Played: 114, Bombs Used: 43, Moves Performed: 12778
 
Duga
Duga
12:15 AM
[rubberduck-vba/Rubberduck] build for commit b6541c0e on unknown branch: AppVeyor build succeeded
> # [Codecov](https://codecov.io/gh/rubberduck-vba/Rubberduck/pull/4851?src=pr&el=h1) Report
> Merging [#4851](https://codecov.io/gh/rubberduck-vba/Rubberduck/pull/4851?src=pr&el=desc) into [next](https://codecov.io/gh/rubberduck-vba/Rubberduck/commit/12a4328000102f3e57bf9952f637b32d956a718a?src=pr&el=desc) will **decrease** coverage by `0.11%`.
> The diff coverage is `69.9%`.


```diff
@@ Coverage Diff @@
## next #4851 +/- ##
========================
[rubberduck-vba/Rubberduck] build for commit b6541c0e on unknown branch: 64.43% (target 0%)
> # [Codecov](https://codecov.io/gh/rubberduck-vba/Rubberduck/pull/4851?src=pr&el=h1) Report
> Merging [#4851](https://codecov.io/gh/rubberduck-vba/Rubberduck/pull/4851?src=pr&el=desc) into [next](https://codecov.io/gh/rubberduck-vba/Rubberduck/commit/12a4328000102f3e57bf9952f637b32d956a718a?src=pr&el=desc) will **decrease** coverage by `0.11%`.
> The diff coverage is `69.9%`.


```diff
@@ Coverage Diff @@
## next #4851 +/- ##
========================
 
 
2 hours later…
Hosch250
Hosch250
2:26 AM
@M.Doerner Yes, there are ways to get the correct logger, and I imagine CW supports them.
There are methods where you can provide a func to get the correct implementation for a request.
It's slightly slower, since it gets called every time you request it. However, if you aren't continuously spamming it (in a tight loop, say), it isn't really noticeable.
@IvenBach Time to follow up with that interview.
 
Duga
Duga
3:13 AM
> @MDoerner loggers can be named anything - if CW can setup the logger name to match the name of the class it's injected into, then it can work. Or the logger name can be hard-coded, but then we would lose the ability to configure per-namespace logger targets (which we're not using afaik)
 

« first day (1748 days earlier)