I've opted to replace it with the default translation key (passwords.password), falling back to the AWS Error Message if no translation exists (as is the case with new L6/7 projects).
This should have no effect on existing projects using Laravel 5.x, whilst remaining compatible with current versions of Laravel.
EDIT: I realise that in other areas of the CognitoClient class, translation paths are specified with no fallback to the exception error message. If you would prefer to keep consistent with that, I can revert the second commit.
The INVALID_PASSWORD const has been removed from Laravel since version 6: https://github.com/laravel/framework/commit/b3e69f1122d1234ccc961a6dad279ddcbbf97b47 https://github.com/laravel/framework/commit/88ec20dbaac61453f1f48e4013af3b3d96ad0729 https://github.com/laravel/laravel/commit/4852f483466bdc83bac132421832d3eec07bcfaf
I've opted to replace it with the default translation key (passwords.password), falling back to the AWS Error Message if no translation exists (as is the case with new L6/7 projects).
This should have no effect on existing projects using Laravel 5.x, whilst remaining compatible with current versions of Laravel.
EDIT: I realise that in other areas of the CognitoClient class, translation paths are specified with no fallback to the exception error message. If you would prefer to keep consistent with that, I can revert the second commit.