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

add extra guidance #1128

Merged
merged 11 commits into from
Aug 7, 2024
Merged

add extra guidance #1128

merged 11 commits into from
Aug 7, 2024

Conversation

IanMayo
Copy link
Contributor

@IanMayo IanMayo commented Aug 2, 2024

Fixes #1122

@IanMayo IanMayo temporarily deployed to rco-review-pr-1128 August 2, 2024 16:57 Inactive
@TahaKhanAbdalli
Copy link
Collaborator

I believe we should display an error message if the user does not enter a password correctly. Currently, users are being created even if the password length is only 8 characters.

@IanMayo
Copy link
Contributor Author

IanMayo commented Aug 5, 2024

I believe we should display an error message if the user does not enter a password correctly. Currently, users are being created even if the password length is only 8 characters.

Great - would you mind adding that please?

@IanMayo
Copy link
Contributor Author

IanMayo commented Aug 6, 2024

Thanks Taha, that works great - I hadn't realised we weren't doing pre-checking on the page.

I remember we had feedback that requested that we include the acceptable special characters in the warning message

I'd like you to add that, please. But, on looking at the code, I see we do provide them in the warning message in one place:
image

I also see that we have multiple instances of the password checking code, and they are not all the same. I'd like the client-side code to all use just one implementation of password checking logic, please.

I don't mind having separate client and server instances of the password checking code - if necessary.

@IanMayo
Copy link
Contributor Author

IanMayo commented Aug 6, 2024

@TahaKhanAbdalli - do you know why we use custom password validation in UserShow.validatePassword?

@IanMayo
Copy link
Contributor Author

IanMayo commented Aug 6, 2024

Thanks Taha - can we also declare the explanatory block as a const in just one place too, please?
image

Aah, we could do that in the same place that we declare the validation schema. Plus, if we do that, we can declare the list of special characters as a constant, and use that constant in both the schema and the explanatory notes :-)

@IanMayo IanMayo temporarily deployed to rco-review-pr-1128 August 6, 2024 14:21 Inactive
@IanMayo
Copy link
Contributor Author

IanMayo commented Aug 7, 2024

Thanks @TahaKhanAbdalli , but I get this runtime error. I presume we need to import the constant.
image

@IanMayo IanMayo temporarily deployed to rco-review-pr-1128 August 7, 2024 07:49 Inactive
@IanMayo IanMayo temporarily deployed to rco-review-pr-1128 August 7, 2024 08:01 Inactive
@TahaKhanAbdalli TahaKhanAbdalli temporarily deployed to rco-review-pr-1128 August 7, 2024 14:06 Inactive
Copy link

sonarqubecloud bot commented Aug 7, 2024

@IanMayo
Copy link
Contributor Author

IanMayo commented Aug 7, 2024

Great, thanks @TahaKhanAbdalli .

@IanMayo IanMayo merged commit feaec01 into main Aug 7, 2024
3 checks passed
@IanMayo IanMayo deleted the 1122_password_complexity_for_add_user branch August 7, 2024 15:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

For add-user, need to indicate password complexity tests
2 participants