-
Notifications
You must be signed in to change notification settings - Fork 2
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
NW6 | Rabia Avci | Full-Stack-Project | Week-2 | New video form #26
Conversation
✅ Deploy Preview for watch-next-cyf ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
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.
All good, nothing to complain about. Good work :)
background-color: #007bff; | ||
color: #fff; | ||
font-size: 16px; | ||
cursor: pointer; |
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.
Is there any particular reason you're setting the cursor to pointer here? It should be pointer by default here https://developer.mozilla.org/en-US/docs/Web/CSS/cursor
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.
When its default it keeps an arrow, i wanted to make it a hand icon when hovering over the element :)
} | ||
|
||
button:hover { | ||
background-color: #0056b3; |
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.
Always nice to have a hover style for buttons.
Overall, I really like what you're doing here, good use of flex and nice touches like border-radius and padding in inputs throughtout
client/src/NewVideoForm.jsx
Outdated
"Content-Type": "application/json", | ||
}, | ||
body: JSON.stringify({ | ||
title: e.target.title.value, |
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 a perfectly acceptable way of handling inputs, especially for a small form, however it's worth being aware that there's a different (not necessarily better, it just serves a different purpose) way of doing this that you may need someday
https://react.dev/reference/react-dom/components/input#controlling-an-input-with-a-state-variable
Signed-off-by: Rabia Avci <[email protected]>
Completed these tasks for this ticket: