-
Notifications
You must be signed in to change notification settings - Fork 14
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
Feature/add about page #212
base: main
Are you sure you want to change the base?
Conversation
@pthan1 just a heads up, the main header and sub header render on top of each other when I view this |
Sorry, I was viewing on a larger screen. I just fixed it.
…On Fri, Oct 22, 2021 at 10:04 PM Wes Galbraith ***@***.***> wrote:
@pthan1 <https://github.com/pthan1> just a heads up, the main header and
sub header render on top of each other when I view this
[image: Screen Shot 2021-10-22 at 10 01 28 PM]
<https://user-images.githubusercontent.com/20004072/138541821-e1f3ea85-b025-4d29-bbec-0c639bb24890.png>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#212 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ATYI2RJNZQLUQ7PZBSQEAQ3UIIX3BANCNFSM5GQZAJDQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
--
Philong Than
|
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.
Please run yarn format
and yarn lint
and make any requested changes.
frontend/src/components/Home.js
Outdated
|
||
export const useStyles = makeStyles((theme) => ({ | ||
// TODO: make custom roundButton component | ||
roundButton: { |
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.
Can you run yarn format
from the frontend directory? That will make the formatting consistent with the main branch and reduce the number of diffs.
While you are there, also run yarn lint
and make any changes the linter suggests. That should get the linter check in github to pass.
frontend/src/components/Home.js
Outdated
<Link to="/about"> | ||
<Button className={classes.aboutFooter}>About</Button> | ||
</Link> |
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 the <Link />
component is adding some funky styling to the <Button />
text.
One way around it is to remove the <Link />
component and use the useHistory
hook to reroute. There might be a better way that explicitly styles the link, so I'm open to other approaches.
<Link to="/about"> | |
<Button className={classes.aboutFooter}>About</Button> | |
</Link> | |
<Button className={classes.aboutFooter} onClick={() => history.push('/about')}> | |
About | |
</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.
I've had luck switching the <Link />
to a <NavLink className={classes.link} />
. What do you think?
frontend/src/components/About.js
Outdated
const classes = useStyles(); | ||
|
||
return ( | ||
<Box className={classes.aboutPage}> |
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.
It would be nice to have a link back to /home
from /about
.
Description
Fixes #189
Type of Change:
Code/Quality Assurance Only
How Has This Been Tested?
Checklist:
Code/Quality Assurance Only