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

Fix: Fix underline issue for login and sign up buttons #190

Closed

Conversation

sachinsom93
Copy link
Contributor

Description

Removed the unnecessary underlines under login and sign Up buttons

Fixes #177

Type of Change:

  • Code

Code/Quality Assurance Only

  • Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

Register page
Login page

Checklist:

  • My PR follows the style guidelines of this project
  • I have performed a self-review of my own code or materials

Code/Quality Assurance Only

  • My changes generate no new warnings

@welcome
Copy link

welcome bot commented Mar 7, 2021

Hello there!👋 Welcome to the project!💖

Thank you and congrats🎉 for opening your first pull request.✨ AnitaB.org is an inclusive community, committed to creating a safe and positive environment.🌸Please adhere to our Code of Conduct and Contribution Guidelines.🙌.We will get back to you as soon as we can.😄

Feel free to join us on AnitaB.org Open Source Zulip Community.💖 We have different streams for each active repository for discussions.✨ Hope you have a great time there!😄

@@ -92,7 +92,13 @@ export default function Login() {
</div>
<div className="row button-group">
<div className="col">
<a className="btn btn-primary" id="registerbtn" href="/register" role="button">Sign Up</a>
<Link
to="/register"
Copy link
Contributor

Choose a reason for hiding this comment

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

please remove unnecessary changes.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Thanks for review this @nlok5923 , but I think it is better to use Link instead of anchor tags to navigate to some other route, what's your view @mtreacy002 ma'am, should I revert this change ?

Copy link
Contributor

Choose a reason for hiding this comment

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

@sachinsom93 @nlok5923 It is better to use Link in react as anchor tags trigger a page refresh which would reset the application states whereas the Link and Navlink of react-router doesn't trigger a page refresh. In single page apps with react, it is better to use Link from react-router.

Copy link

Choose a reason for hiding this comment

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

@nlok5923 Just as an extra opinion, I agree with @sachinsom93 and @Rahulm2310 on the use of Link tags in place of a in React for the same reasons specified above. Generally speaking, the Link tags are better placed for in-app navigation(relative urls) and the a tags for external links(absolute urls).

@@ -254,7 +254,13 @@ export default function Register() {
</div>
<div className="row button-group">
<div className="col">
<a className="btn btn-primary" id="loginbtn" href="/login" role="button">Login</a>
<Link
to="/login"
Copy link
Contributor

Choose a reason for hiding this comment

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

here also

Copy link
Contributor

@nlok5923 nlok5923 left a comment

Choose a reason for hiding this comment

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

please refer to the comments and also i think you should not compare package-lock.json what's your view @mtreacy002 ma'am.

Body: Text underline on the Login and Sign Up(blue) buttons(ISSUE anitab-org#177)
@Rahulm2310
Copy link
Contributor

@sachinsom93 Please remove package-lock.json from the commit as it has unnecessary changes which need not to be pushed.

@mtreacy002 mtreacy002 added Category: Coding Changes to code base or refactored code that doesn't fix a bug. Category: User Interface Improvements or additions to design. Status: Changes Requested Changes are required to be done by the PR author. Type: Bug Bug or Bug fixes. labels Mar 8, 2021
@mtreacy002
Copy link
Member

@sachinsom93 , can you please give us an update on this?

Copy link
Member

@mtreacy002 mtreacy002 left a comment

Choose a reason for hiding this comment

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

@sachinsom93 , as per @Rahulm2310 suggested, can you please remove this package-lock.json from the commit (not to delete it from your local)?

@sachinsom93
Copy link
Contributor Author

@sachinsom93 , as per @Rahulm2310 suggested, can you please remove this package-lock.json from the commit (not to delete it from your local)?

@mtreacy002 I will do it as soon as possible.

@HeroicHitesh
Copy link
Member

@mtreacy002 I will do it as soon as possible.

@sachinsom93 Can you please share updates on your progress?

package.json Outdated
@@ -12,7 +12,7 @@
"react": "^16.13.1",
"react-dom": "^16.13.1",
"react-router-dom": "^5.2.0",
"react-scripts": "^3.4.3"
"react-scripts": "^4.0.3"
Copy link
Member

@mtreacy002 mtreacy002 Mar 19, 2021

Choose a reason for hiding this comment

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

is this update needed, @sachinsom93 ? Do you have any reason why we need this? This is also the reason why the package-lock.json is changed.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@mtreacy002 , I didn't update it manually, it got updated when I use "npm install" at the time of project setup.

Copy link
Contributor

Choose a reason for hiding this comment

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

@sachinsom93 We already have an issue open for updating the react-scripts version (#194). So, please revert these changes to the package.json and package-lock.json here.

This reverts commit 2d03ae5.
@Rahulm2310
Copy link
Contributor

Rahulm2310 commented Mar 22, 2021

@sachinsom93 , as per @Rahulm2310 suggested, can you please remove this package-lock.json from the commit (not to delete it from your local)?

@sachinsom93 you were requested to not include package-lock.json in the commit (not to delete package-lock.json). Also now I am unable to see your changes to the buttons.

The earlier changes you made to the buttons were correct. We just wanted you to not push unnecessary changes ( made to package.json and package-lock.json). If you have any doubts, then please ask.

@mtreacy002
Copy link
Member

@sachinsom93 , can you please give us an update on this?

@sachinsom93
Copy link
Contributor Author

@sachinsom93 , can you please give us an update on this?

@mtreacy002, sorry for being inactive, I tried to revert the changes but it didn't work. So, I am going to create new pr for the same.
Will it work ?

@vj-codes
Copy link
Member

@sachinsom93 you can make a new PR
Also, your fork is 7 commits behind, just make sure it's in sync with develop branch before creating a new one:)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Category: Coding Changes to code base or refactored code that doesn't fix a bug. Category: User Interface Improvements or additions to design. Status: Changes Requested Changes are required to be done by the PR author. Type: Bug Bug or Bug fixes.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Bug: text underline on the Login & Sign Up (blue) buttons
7 participants