-
Notifications
You must be signed in to change notification settings - Fork 133
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove supportOldDangerousPassword support #867
Remove supportOldDangerousPassword support #867
Conversation
@omerimzali, Line 321 in 1d9a659
Also, run the following command to fix the code style: composer cs-fix And you must GPG-sign your work, certifying that you either wrote the work or otherwise have the right to pass it on to an open-source project. See https://github.com/codeigniter4/CodeIgniter4/blob/develop/contributing/workflow.md#gpg-signing-old-commits. |
@datamweb Allright I'll try these and update the PR. |
Sorry, Ok. Edit:
|
e0d2c5c
to
49a8247
Compare
@datamweb I repushed the PR with sign. It was not easy to sign last 3 commits I'm not sure if it went well. and with change of this line below like you mentioned. I use composer-fix but here's the thing, I don't really know why did you ask to change this phpstan config. 1d9a659 Feel free to reject the PR I can create a fresh one if it's not okay. |
The reason for this request was the failure in examination phpstan. In fact, we had already suppressed the number of 9 errors detected by PHPStan. With this PR you have removed the following code: public function testCheckSuccessOldDangerousPassword(): void
{
/** @var Auth $config */
$config = config('Auth');
$config->supportOldDangerousPassword = true; // @phpstan-ignore-line
fake(
UserIdentityModel::class,
[
'user_id' => $this->user->id,
'type' => Session::ID_TYPE_EMAIL_PASSWORD,
'secret' => 'foo@example.com',
'secret2' => '$2y$10$WswjNNcR24cJvsXvBc5TveVVVQ9/EYC0eq.Ad9e/2cVnmeSEYBOEm',
]
);
$result = $this->auth->check([
'email' => 'foo@example.com',
'password' => 'passw0rd!',
]);
$this->assertInstanceOf(Result::class, $result); // This causes an error
$this->assertTrue($result->isOK());
$foundUser = $result->extraInfo();
$this->assertSame($this->user->id, $foundUser->id);
} Therefore, one error will be less. Regarding command As you can see now, everything turned green: |
Please refer to the link below: |
dbb448b
to
652d639
Compare
652d639
to
157f21f
Compare
@datamweb Thank you for all these explanations. Specially on PHPStan part. I was confused at first about replacing 9 to 8. |
@datamweb 🙏 PR need a reviewer and approving review by reviewers, but will you wait to merge because of the scope of this PR? |
@omerimzali I added a ref link to your PR description, but haven't had time to review it carefully yet. @kenjis, what's the next version? |
The next version is 1.0.0-beta.7. |
@datamweb thank you, feel free to ping me for any changes. |
@omerimzali Now some GitHub Acton checks are failed. Can you rebase? We are going to release v1.0.0 soon. |
No feedback. |
Fixes #771
Ref: ea9688d
Description
I removed supportOldDangerousPassword. And also there is no usage of verifyDanger() anymore I also deleted it. I didn't update the docs because docs already have the information about deprecation for version 1.0.0 release.
Checklist: