-
Notifications
You must be signed in to change notification settings - Fork 163
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
Implement minimum length for passwords in account creation #4353
Implement minimum length for passwords in account creation #4353
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @cerdo03! Generally the code looks good and works as expected, thanks. However it appears that one of the scenarios specified on the issue will fail
.....In development mode, the password
a
should still work.
@bjester will clarify on this.
Also, noting that there are a few failing tests that will need fixing before a merge.
contentcuration/contentcuration/frontend/accounts/pages/Create.vue
Outdated
Show resolved
Hide resolved
contentcuration/contentcuration/frontend/accounts/pages/Create.vue
Outdated
Show resolved
Hide resolved
….vue Co-authored-by: Blaine Jester <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see some print
statements and a lot of commented code.
Hello @cerdo03, are you still planning to follow-up here or would it be better to close the pull request? |
@cerdo03 Thank you for taking this on. You got it most of the way there, and I wrapped it up. Some of the backend code was quite confusing in how it worked. |
@@ -291,10 +310,12 @@ | |||
]; | |||
}, | |||
usageRules() { | |||
return [() => (this.form.uses.length ? true : this.$tr('fieldRequiredMessage'))]; | |||
/* eslint-disable-next-line kolibri/vue-no-undefined-string-uses */ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is nolonger necessary as fieldRequired
exists. There's a few other places to clean this up too.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unfortunately, this is required. The linting rule does not properly understand this is an external translator
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Generally, the implemenation looks correct to me. There seem to be a few linting comments that may require cleanup too. Unless it is deliberate to have them, we should be good to go. Also, the failing test needs to be looked into before the merge.
Hi @cerdo03! Are you still interested in contributing to this pr, or we should reassign it? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Generally, the implementation looks correct to me. Manual QA also checkouts. However, it looks like
is still missing. @bjester is still a requirement for this pr?
My comment there was a bit ambiguous. I meant that it should still work for login. That should still be the case |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@AlexVelezLl adding a little blocker so that the issue here can be address too!
@akolson I just tested this and the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approving this after a chat with Blaine. The context of this was based on how historical data should be handled, and the pr addresses this. Thanks again @AlexVelezLl for finishing this off!
Summary
Description of the change(s) you made
Fixes #4142
I have implemented password length validation on password1 field. Password should be at least 8 characters long otherwise it would throw an error that "Password should be atleast 8 characters long".
Manual verification steps performed
Comments
Does the validation need to implemented on backend as well?
Contributor's Checklist
PR process:
CHANGELOG
label been added to this PR. Note: items with this label will be added to the CHANGELOG at a later timedocs
label has been added if this introduces a change that needs to be updated in the user docs?requirements.txt
files also included in this PRStudio-specifc:
notranslate
class been added to elements that shouldn't be translated by Google Chrome's automatic translation feature (e.g. icons, user-generated text)pages
,components
, andlayouts
directories as described in the docsTesting:
Reviewer's Checklist
This section is for reviewers to fill out.
yarn
andpip
)