-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
fix-#257: Implemented show/hide password functionality #364
fix-#257: Implemented show/hide password functionality #364
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Hey @rushil-b-patel! Thanks for sticking to the guidelines! High five! 🙌🏻 |
Hey @rushil-b-patel! Thanks for sticking to the guidelines! High five! 🙌🏻 |
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.
LGTM, the first commit "revert" doesn't follow the guidelines, but i'll let it slide. Kindly address the review comments
backend/app.js
Outdated
@@ -16,7 +16,7 @@ app.use(cors({ | |||
credentials: true | |||
})); | |||
app.use(express.json()); | |||
app.use(express.urlencoded({ extended: true })); | |||
app.use(express.urlencoded()); |
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.
why this change
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.
this is what I was saying that I commited that payload vala change but I tried to undo that commit through revert but I don't I didn't find my way but managed to undo in this commit. So it will the same the app.js (backend) won't change.
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.
payload vala change, i didn't get.
But if this is unexpected and want to get back, make a new commit reverting the changes
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.
umm what I was saying is that I made a commit changing the app.use(express.urlencoded()); to app.use(express.urlencoded({ extended: true })); but I revert the changes while addressing this password vala issue so in this commit it will get back to normal app.use(express.urlencoded()); which is already there in the main branch, so it won't affect.
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.
Oh okay, you are saying previously you were the one who made this changes is 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.
umm what I was saying is that I made a commit changing the app.use(express.urlencoded()); to app.use(express.urlencoded({ extended: true }));
This never happened in the main branch, it might be in the private branch
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.
Just change it back to this so that I can merge
app.use(express.urlencoded({ extended: true }));
Just do this,
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.
yes it was in private repo.
You want to change from app.use(express.urlencoded()); to this app.use(express.urlencoded({ extended: true }));..? @krishnaacharyaa
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.
any update...? @krishnaacharyaa
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 have updated long time ago with the emoji
className="absolute inset-y-0 right-0 flex items-center pr-3 text-sm leading-5" | ||
> | ||
<img src={passwordVisible ? EyeOffIcon : EyeIcon} alt="Toggle-visibility" className="w-5 h-5" /> | ||
</button> |
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.
{passwordVisible ? EyeOffIcon : EyeIcon} ideally should be {passwordVisible ? EyeIcon : EyeOffIcon}
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.
ohh My bad, yes you are correct. Let me change that...
type="button" | ||
onClick={() => setPasswordVisible(!passwordVisible)} | ||
className="absolute inset-y-0 right-0 flex items-center pr-3 text-sm leading-5" | ||
> |
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.
Kindly make sure if this works in the mobile screen as well, can you add the video recorded for the mobile screen as well
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.
sure @krishnaacharyaa
Hey @rushil-b-patel! Thanks for sticking to the guidelines! High five! 🙌🏻 |
good to go...! @krishnaacharyaa |
Good to go.. @krishnaacharyaa ...! |
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.
LGTM, thanks
Summary
Implemented the show/hide password functionality with state & react icons.
Description
Images
passwordVisibility.webm
(it supports the mobile responsive also so no need to change any thing :) )
Issue(s) Addressed
Closes #257
Prerequisites