docs: add annotation for psalm #518
Conversation
The current comment content does not match what the code is doing. Please feel free to clean up or let me know any suggestions. Thank you!
Co-authored-by: kenjis <kenji.uui@gmail.com>
To reduce psalm issues.
docs: add code block language for fix website
…ord-hashing config: update ARGON2I/ARGON2ID Algorithm options
docs: fix property notation
Other codes specify encoding. Co-authored-by: Pooya Parsa Dadashi <pooya_parsa_dadashi@yahoo.com>
Co-authored-by: John Paul E. Balandan, CPA <paulbalandan@gmail.com>
PHPStan is the first analyzer for our project.
…ngth fix: minimum password length check
docs: add annotation for psalm
|
Something went wrong with this PR. I hit the merge button of this PR on GitHub, but I got a form to select my email address. But when I see the commit log of |
|
Very odd! I've had something similar happen when I accidentally fork another PR off a feature branch, and if the second PR gets merged and then feature is rebased it can "go away". I'm not sure that is what happened here though looking at the weird vomit history of this PR. End result appears good, so 🤷♂️ |
|
If this PR was used as base for another PR that got merged first, then this PR is deemed automatically merged. Just read it recently in Github docs. |
|
This is not used as base for another PR. It seems this PR was merged into develop, but I rebased this branch (with the develop already merged this) and force pushed. The last commit in this PR is However, I'm still not sure what happened, but as a result, the develop branch looks fine. |
5 participants
To reduce psalm issues.
Before: 803 other issues found.
After:
684681 other issues found.