Create rule S7946: Logging statements should use lazy evaluation to avoid performance overhead

[github-actions[bot]]

You can preview this rule here (updated a few minutes after each push).

Review

A dedicated reviewer checked the rule description successfully for:

• [ ] logical errors and incorrect information
• [ ] information gaps and missing content
• [ ] text style and tone
• [ ] PR summary and labels follow the guidelines

[sonarqube-next[bot]]

Quality Gate passed for 'rspec-tools'

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
0 Dependency risks
No data about Coverage
No data about Duplication

See analysis details on SonarQube

[sonarqube-next[bot]]

Quality Gate passed for 'rspec-frontend'

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
0 Dependency risks
No data about Coverage
No data about Duplication

See analysis details on SonarQube

[joke1196]

I have rewritten the rule to make more sense sadly this rule does not apply to Python 3.14 anymore.

[sonarqube-next[bot]]

Quality Gate passed for 'rspec-frontend'

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
1 Dependency risk
No data about Coverage
No data about Duplication

See analysis details on SonarQube

[sonarqube-next[bot]]

Quality Gate passed for 'rspec-tools'

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
0 Dependency risks
No data about Coverage
No data about Duplication

See analysis details on SonarQube

[joke1196]

We decide to not implement such a rule as the value is too low and the risk of FP too high.