php-psr-log 1.1.2-1 source package in Ubuntu
Changelog
php-psr-log (1.1.2-1) unstable; urgency=medium [ Cees-Jan Kiewiet ] * Return string from DummyTest::__toString -- David Prévot <email address hidden> Sun, 03 Nov 2019 16:47:50 -1000
Upload details
- Uploaded by:
- Debian PHP PEAR Maintainers
- Uploaded to:
- Sid
- Original maintainer:
- Debian PHP PEAR Maintainers
- Architectures:
- all
- Section:
- misc
- Urgency:
- Medium Urgency
See full publishing history Publishing
| Series | Published | Component | Section | |
|---|---|---|---|---|
| Focal | release | universe | misc |
Downloads
| File | Size | SHA-256 Checksum |
|---|---|---|
| php-psr-log_1.1.2-1.dsc | 1.7 KiB | c4180e4b53739b3702727258b571febf4cca815d4822c8453762762345510ffc |
| php-psr-log_1.1.2.orig.tar.gz | 5.6 KiB | b55f9268b804e2c6cf72fc9b81296ca508713a014af9f82186e70eb707970049 |
| php-psr-log_1.1.2-1.debian.tar.xz | 3.3 KiB | 30492446219fe5faa088ff9a3e379869816e058a2def46cc9928ffc40de865cb |
Available diffs
- diff from 1.1.1-1 to 1.1.2-1 (773 bytes)
No changes file available.
Binary packages built by this source
- php-psr-log: common interface for logging libraries
The main goal is to allow libraries to receive a Psr\Log\
LoggerInterface object
and write logs to it in a simple and universal way. Frameworks and CMSs that
have custom needs MAY extend the interface for their own purpose, but SHOULD
remain compatible with this document. This ensures that the third-party
libraries an application uses can write to the centralized application logs.
.
The LoggerInterface exposes eight methods to write logs to the eight RFC 5424
levels (debug, info, notice, warning, error, critical, alert, emergency).
.
A ninth method, log, accepts a log level as first argument. Calling this method
with one of the log level constants MUST have the same result as calling the
level-specific method. Calling this method with a level not defined by this
specification MUST throw a Psr\Log\InvalidArgument Exception if the
implementation does not know about the level. Users SHOULD NOT use a custom
level without knowing for sure the current implementation supports it.
.
Note that this is not a logger of its own. It is merely an interface that
describes a logger. See the specification for more details.
