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

Melissa Pena - Cheetahs #118

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Melissa Pena - Cheetahs #118

wants to merge 3 commits into from

Conversation

melipena
Copy link

No description provided.

Copy link

@kendallatada kendallatada left a comment

Choose a reason for hiding this comment

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

Hi Melissa! Your submission has been scored as green. You can find my comments in your code. Nice work! 😊

import chatMessages from './data/messages.json';

const App = () => {
const chatCopy =[]
for (const message of chatMessages){
chatCopy.push(message)

Choose a reason for hiding this comment

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

Glad to see you're trying to ensure you don't modify the original data! Imports are actually read only though. So it's safe to use the message data directly without making a copy first.

Side note - the push() method doesn't actually create a copy of the data. It passes a reference to the original object. This means if you make changes to the "copy", the original will also be updated. You don't see this causing any issues in your code since imports are read only.

In the future, if you need to make a copy of an object, I'd recommend using the spread operator. Here's a great guide on shallow copies vs deep copies in JS: https://code.tutsplus.com/articles/the-best-way-to-deep-copy-an-object-in-javascript--cms-39655

const [chatData, setChatData]= useState(chatCopy)

const updateLikes = (id, updatedLike) => {
console.log('updatelikes is being called');

Choose a reason for hiding this comment

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

Be sure to remove unused code, print tests, and any comments that shouldn't be published before finalizing a project. It's good practice to keep a clean main branch that's production ready. This helps with the readability and maintainability of a project. 🧹😌

return (
<div id="App">
<header>
<h1>Application title</h1>
<h1>Instant Messenger</h1>
<h2>{countLikes()} ❤️s</h2>

Choose a reason for hiding this comment

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

Nice job calculating likes! Right now, your app will re-calculate your likes count every time your App component re-renders. This totally works, but it could slow down performance as the number of messages begins to grow larger since countLikes() has an O(n) time complexity. Consider how you could refactor your code to improve performance.

<button className="like">🤍</button>
<p>{body}</p>
<p className="entry-time"><TimeStamp time={timeStamp}/></p>
<button className="like" onClick={() => updateLikes(id, !liked)}>

Choose a reason for hiding this comment

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

Nice job adding the callback function in an anonymous function here!

sender:PropTypes.string.isRequired,
body:PropTypes.string.isRequired,
timeStamp:PropTypes.string.isRequired,
updateLikes:PropTypes.func

Choose a reason for hiding this comment

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

Small note, but I would recommend setting id and updateLikes as required in your prop types since they are needed for the like button to work.

import ChatEntry from './ChatEntry';
import PropTypes from 'prop-types';

const ChatLog = ({entries,updateLikes}) => {

Choose a reason for hiding this comment

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

Make sure you're cleaning up the code style before finalizing a project! This component seems to be using 4 space tabs instead of the 2 space convention as well as some other small style inconsistencies. Good code style is important for readability and maintainability. 🧹 😌

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.

2 participants