Conversation
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## master #1438 +/- ##
============================================
- Coverage 45.48% 38.53% -6.96%
+ Complexity 3692 3482 -210
============================================
Files 158 139 -19
Lines 12292 10373 -1919
============================================
- Hits 5591 3997 -1594
+ Misses 6701 6376 -325 |
08ebb9c to
64fca25
Compare
8c7e372 to
88a231b
Compare
83c78e6 to
f3eea7b
Compare
7a53fc8 to
d73ae47
Compare
e5c0e21 to
d5616df
Compare
2e6ab04 to
32f9acc
Compare
7e3ea19 to
2523634
Compare
5b84489 to
e632526
Compare
8ac729b to
a16cf6e
Compare
fc454de to
7ac76ae
Compare
29f7b69 to
1a911ce
Compare
c7c8357 to
fdbe001
Compare
|
I started looking into this and #371 Another option these days is to use the Symfony logging I am still looking at if trying to use the injection stuff might help. I have a little example of using the monolog to back the logs but it might make sense to use the Symfony logging so we can slot in whatever we want there and SSP is somewhat shielded from it. OTOH if we gain enough to invest the time into this right now or focus on other enhancements and 3.x first. I mainly got here looking at some of the older PRs. |
|
I'm all in favour of using symfony for this! |
This checks some of the boxes in #371:
$contextparameter to all the methods defined byPsr\Log\LoggerInterface.\SimpleSAML\Loggerclass extendPsr\Log\AbstractLogger.\SimpleSAML\Logger::log()method public and make it throw a\Psr\Log\InvalidArgumentExceptionif the log level is unknown.