Skip to content
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

Handling asynchronous prestashop.checkPasswordScore #67

Merged
merged 1 commit into from
Oct 25, 2022

Conversation

Oksydan
Copy link
Contributor

@Oksydan Oksydan commented Oct 23, 2022

Questions Answers
Description? Changes usePasswordPolicy.js to handle changes made in PrestaShop/PrestaShop#30104. prestashop.checkPasswordScore right now is returning promise instead of password score.
Type? improvement
BC breaks? no
Deprecations? no
Fixed ticket? Fixes #30088
How to test? Follow instruction wrote here PrestaShop/PrestaShop#30104.
Possible impacts? Password policy feature only.

Copy link

@NeOMakinG NeOMakinG left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🍬

@khouloudbelguith khouloudbelguith self-assigned this Oct 24, 2022
@jolelievre jolelievre added the Waiting for QA Status: Waiting for QA feedback label Oct 24, 2022
Copy link
Contributor

@khouloudbelguith khouloudbelguith left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @Oksydan,

As commented here: PrestaShop/PrestaShop#30104 (review)
When I use this physical_uri= /test/80x/ => NOK

Thanks!

@khouloudbelguith khouloudbelguith added Waiting for author QA ✔️ Status: QA-Approved and removed Waiting for QA Status: Waiting for QA feedback Waiting for author labels Oct 24, 2022
@kpodemski kpodemski merged commit 1ee5f45 into PrestaShop:develop Oct 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
QA ✔️ Status: QA-Approved
Projects
None yet
Development

Successfully merging this pull request may close these issues.

New password policy fix causes core.js to be gigantic
5 participants