CVE and update status of the FreeBSD ports tree3,864 unaddressed CVEs in 671 portsAll times are CET
Port details

devel/p5-Dancer2-Plugin-LogReport 2.03

Logging, exceptions and translations in Dancer2 via Log::Report

Maintainer
sunpoet@FreeBSD.org
Packages
latest: 2.03
Upstream
up to date
Last update
to 2.03 · 982bd00e01
Quarterly
2026Q4: 2.03
WWW
https://metacpan.org/dist/Dancer2-Plugin-LogReport
Links
cgit · VuXML

Unaddressed and VuXML only (0)

No unaddressed CVE and nothing reported by pkg audit for the packaged version 2.03.

Fixed (0)

No VuXML entries for this package.

Problem reports (0) · open in Bugzilla, most recently changed first

None.

Commits (2)

Po-Chuan Hsieh (sunpoet) · 2.03
devel/p5-Dancer2-Plugin-LogReport: Update to 2.03

Changes:	https://metacpan.org/dist/Dancer2-Plugin-LogReport/changes
982bd00e01
Po-Chuan Hsieh (sunpoet) · 2.02
devel/p5-Dancer2-Plugin-LogReport: Add p5-Dancer2-Plugin-LogReport 2.02

Dancer2::Plugin::LogReport provides easy access to the extensive logging
facilities provided by Log::Report. Along with Dancer2::Logger::LogReport, this
brings together all the internal Dancer2 logging, handling for expected and
unexpected exceptions, translations and application logging.

Logging is extremely flexible using many of the available dispatchers. Multiple
dispatchers can be used, each configured separately to display different
messages in different formats. By default, messages are logged to a session
variable for display on a webpage, and to STDERR.

Messages within this plugin use the extended Dancer2::Logger::LogReport::Message
class rather than the standard Log::Report::Message class.

Note that it is currently recommended to use the plugin in all apps within a
Dancer2 program, not only some. Therefore, wherever you use Dancer2 you should
also use Dancer2::Plugin::LogReport. This does not apply if using the same app
name (use Dancer2 appname, 'Already::Exists'). In all other modules, you can
just use Log::Report.
2342e946a9