No new problems found by Qodana for PHP
Qodana for PHP
It seems all right 👌
No new problems were found according to the checks applied
💡 Qodana analysis was run in the pull request mode: only the changed files were checked
☁️ View the detailed Qodana report
Contact Qodana team
Contact us at [email protected]
- Or via our issue tracker: https://jb.gg/qodana-issue
- Or share your feedback: https://jb.gg/qodana-discussions
Details
This result was published with Qodana GitHub Action
Annotations
Check notice on line 35 in src/State/ResetPasswordProcessor.php
github-actions / Qodana for PHP
Efferent coupling between objects
\[EA\] High efferent coupling (20).
Check warning on line 62 in src/State/ResetPasswordProcessor.php
github-actions / Qodana for PHP
Null reference
\[EA\] Null pointer exception may occur here.
Check warning on line 103 in src/State/ResetPasswordProcessor.php
github-actions / Qodana for PHP
Undefined class
Undefined class 'AdminEvents'
Check warning on line 23 in src/State/ResetPasswordProcessor.php
github-actions / Qodana for PHP
Undefined class
Undefined class 'LostPasswordEvent'
Check warning on line 22 in src/State/ResetPasswordProcessor.php
github-actions / Qodana for PHP
Undefined class
Undefined class 'AdminEvents'
Check warning on line 102 in src/State/ResetPasswordProcessor.php
github-actions / Qodana for PHP
Undefined class
Undefined class 'LostPasswordEvent'
Check warning on line 23 in src/State/ResetPasswordProcessor.php
github-actions / Qodana for PHP
Undefined namespace
Undefined namespace 'Login'
Check warning on line 22 in src/State/ResetPasswordProcessor.php
github-actions / Qodana for PHP
Undefined namespace
Undefined namespace 'Event'
Check notice on line 45 in src/State/ResetPasswordProcessor.php
github-actions / Qodana for PHP
Return type hint can be used
\[EA\] ': ResetPasswordRequest' can be declared as return type hint.
Check notice on line 86 in src/State/ResetPasswordProcessor.php
github-actions / Qodana for PHP
General exception is thrown
\[EA\] \\Exception is too general. Consider throwing one of SPL exceptions instead.