Skip to content

fix #84 Rename LogRecord::hasContext() to hasContextInfo() (log context no longer displayed) - #87

Merged
njoubert-cleverage merged 1 commit into
mainfrom
84-fix
Oct 2, 2026
Merged

njoubert-cleverage merged 1 commit into
mainfrom
84-fix

Conversation

@njoubert-cleverage

Copy link
Copy Markdown
Member

Description

Fixes a regression of #84 (PR #86, not released yet).

LogRecord::hasContext() (added by #84) is picked by the Symfony PropertyAccessor to read the context property (it tries getContext(), isContext(), then hasContext()): EasyAdmin then gets true instead of the context array, and the "Context" field of the log detail page is empty. Found by the functional tests of #81.

  • LogRecord::hasContext() renamed to hasContextInfo() (as the "Has context info ?" column), used by LogRecordCrudController; contextIsEmpty() (deprecated) points to it
  • LogRecordTest: the context property is readable by the PropertyAccessor (returns true without the fix)
  • CHANGELOG Latest entry of LogRecord::contextIsEmpty() returns true when the context is not empty #84 updated

No deprecation needed: hasContext() was never released (v3.0.2 does not contain #84).

Requirements

  • Documentation updates
    • Reference
    • Changelog
  • Unit tests

Breaking changes

None (unreleased method).

🤖 Generated with Claude Code

…rtyAccessor used it to read the context property, the context was no longer displayed on the log detail page

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@njoubert-cleverage
njoubert-cleverage merged commit 949a763 into main Oct 2, 2026
18 checks passed
@njoubert-cleverage
njoubert-cleverage deleted the 84-fix branch October 2, 2026 14:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant