feat: log expression compilation errors and replace single quotes in ExpressionHandler

[Copilot]

• Add Logger property to ExpressionHandler (under #if !NET452) and log warnings when expression compilation fails in TryCompileExpression
• Replace single quotes with double quotes in expressions to handle known DynamicExpresso issue — moved to EnforceView.CreateWithMatcher so normalization happens once at view creation rather than on every Invoke call
• Propagate Logger from Enforcer to ExpressionHandler via property setters only (not on every enforce call)
• Update MockLogger to capture log entries in a Logs list for test assertions
• Fix MockLogger to pass exception (not null) to formatter so exception details appear in log messages
• Add tests to verify single-quote replacement and warning logging behavior
• All 365 tests pass

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Logging ExpressionHandler exception(s)</issue_title>
<issue_description>1. Multiple times I was stumbled why some policies wouldn't work - until I realized that the expressions had some invalid syntax yet the TryExpressionBuilder was hiding the exception:

https://github.com/casbin/Casbin.NET/blob/6acec871fbabfd6aa3008c27edd57d3a21f3999e/Casbin/Evaluation/ExpressionHandler.cs#L120

IMO we should log the error using the standard logger... I am also not sure why there is no try&catch around CompileExpression() - as there could be errors in there as well.

2. FYI - the actual Interpretor (DynamicExpresso) has known issues with single quotes - might be useful to change those before the actual evaluation to double quotes, e.g.

expressionString = expressionString.Replace('\'', '"');

Thanks</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Logging ExpressionHandler exception(s) #396

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[sagilio]

@copilot Maybe it is necessary to set the logger at every enforce call

[Copilot]

@copilot Maybe it is necessary to set the logger at every enforce call

Fixed in 16f3bc0. The logger is now only propagated when Enforcer.Logger or Enforcer.Model is set (via property setters), not on every enforce call.

[sagilio]

@copilot Plz fix the PR title for the Semantic PR check

[Copilot]

@copilot Plz fix the PR title for the Semantic PR check

I'm unable to directly update the PR title through the tools available to me. Could you please rename the PR title to follow Conventional Commits format? The suggested title would be:

feat: log expression compilation errors and replace single quotes in ExpressionHandler

[sagilio]

@copilot Can you fix this: Semantic / Semantic check (pull_request)

[Copilot]

@copilot Can you fix this: Semantic / Semantic check (pull_request)

The Semantic check was failing because the PR title lacked a conventional commit prefix. The title was updated to feat: ... and I pushed commit 7a4f4f6 to trigger a new CI run — the Semantic check should now pass.

[sagilio]

@copilot Plz move expressionString.Replace to create enforcer view

[Copilot]

@copilot Plz move expressionString.Replace to create enforcer view

Done in d8f91fa. The Replace('\'', '"') is now applied at the start of EnforceView.CreateWithMatcher, normalizing the matcher string once at view creation time. It's been removed from ExpressionHandler.Invoke.

[sagilio]

LGTM

[github-actions]

🎉 This PR is included in version 2.20.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀