Skip to content

CP-17047 logger trace#17073

Merged
niden merged 4 commits into
5.0.xfrom
CP-17047-logger-trace
Jun 5, 2026
Merged

CP-17047 logger trace#17073
niden merged 4 commits into
5.0.xfrom
CP-17047-logger-trace

Conversation

@niden
Copy link
Copy Markdown
Member

@niden niden commented Jun 5, 2026

Hello!

In raising this pull request, I confirm the following:

  • I have read and understood the Contributing Guidelines
  • I have checked that another pull request for this purpose does not exist
  • I wrote some tests for this PR
  • I have updated the relevant CHANGELOG
  • I have created a PR for the documentation about this change

Added a trace() method to Phalcon\Logger\Logger together with a new TRACE log level (value 9, label trace) on Phalcon\Logger\Enum and Phalcon\Logger\AbstractLogger. trace() is opt-in: the default threshold stays CUSTOM (8), so trace messages are emitted only after setLogLevel(Enum::TRACE). The existing CUSTOM level and its custom label (the unknown-level bucket) are unchanged.

Thanks

niden added 4 commits June 4, 2026 19:50
Assisted-by: Claude Code
Assisted-by: Claude Code
Assisted-by: Claude Code
@niden niden requested a review from Jeckerson June 5, 2026 02:33
@niden niden self-assigned this Jun 5, 2026
@niden niden added new feature request Planned Feature or New Feature Request 5.0 The issues we want to solve in the 5.0 release labels Jun 5, 2026
@niden niden merged commit 82bfd81 into 5.0.x Jun 5, 2026
192 checks passed
@niden niden deleted the CP-17047-logger-trace branch June 5, 2026 12:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

5.0 The issues we want to solve in the 5.0 release new feature request Planned Feature or New Feature Request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant