Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions src/App.css
Original file line number Diff line number Diff line change
Expand Up @@ -26,6 +26,7 @@
display: inline-block;
}


#App header section {
background-color: #e0ffff;
}
Expand All @@ -38,6 +39,8 @@
font-size:0.8em;
padding-left: 1em;
padding-right: 1em;
font-size: 1em;
font-weight: bold;
}

#App #heartWidget {
Expand Down
47 changes: 43 additions & 4 deletions src/App.js
Original file line number Diff line number Diff line change
@@ -1,19 +1,58 @@
import React from 'react';
import './App.css';
import chatMessages from './data/messages.json';
import ChatLog from './components/ChatLog.js';
import { useState } from 'react';

Choose a reason for hiding this comment

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

We could combine the react imports into a single line:

import React, { useState } from 'react';



const App = () => {
const sender1 = chatMessages[0].sender;
const sender2 = chatMessages[1].sender;
const [chatEntries, setChatEntries] = useState(chatMessages);
const [likes, setLikes] = useState(0);

Choose a reason for hiding this comment

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

Since the liked status of a message lives in the chatEntries data we should avoid holding an extra piece of state that we need to manually keep in sync. We can use a higher order function like array.reduce to take our list of messages and reduce it down to a single value:

// This could be returned from a helper function
// totalLikes is a variable that accumulates a value as we loop over each entry in chatEntries
const likesCount = chatEntries.reduce((totalLikes, currentMessage) => {
    // If currentMessage.liked is true add 1 to totalLikes, else add 0
    return (totalLikes += currentMessage.liked ? 1 : 0);
}, 0); // The 0 here sets the initial value of totalLikes to 0


const incLikes = () =>{
setLikes(likes + 1);
};

const decLikes = () =>{
setLikes(likes - 1);
};

const updateEntry = updatedEntry => {
const entries = chatEntries.map(entry => {
if (entry.id === updatedEntry.id) {
if (updatedEntry.liked) {
incLikes();
}
else {
decLikes();
}
return updatedEntry;
} else {
return entry;
}
});
setChatEntries(entries)
}

return (
<div id="App">
<header>
<h1>Application title</h1>
<h1>Chat between {sender1} and {sender2}</h1>
<section>
<p className='widget'>{likes} ❤️s</p>
</section>
</header>
<main>
{/* Wave 01: Render one ChatEntry component
Wave 02: Render ChatLog component */}
{<ChatLog
entries = {chatEntries}
onUpdateEntry = {updateEntry}
sender1 = {sender1} // local sender
/>}
</main>
</div>
);
};

export default App;
export default App;
3 changes: 2 additions & 1 deletion src/components/ChatEntry.css
Original file line number Diff line number Diff line change
Expand Up @@ -97,4 +97,5 @@ button {

.chat-entry.remote .entry-bubble:hover::before {
background-color: #a9f6f6;
}
}

40 changes: 31 additions & 9 deletions src/components/ChatEntry.js
Original file line number Diff line number Diff line change
@@ -1,22 +1,44 @@
import React from 'react';
import './ChatEntry.css';
import PropTypes from 'prop-types';
import TimeStamp from './TimeStamp';

const ChatEntry = (props) => {

const onUpdateButtonClick = () => {
const updatedEntry = {
id: props.id,
sender: props.sender,
timeStamp: props.timeStamp,
body: props.body,
liked: !props.isLiked,
sender1: props.localSender
};
props.onUpdate(updatedEntry);
};
Comment on lines +7 to +17

Choose a reason for hiding this comment

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

I would consider passing the id of the message clicked to props.onUpdate and having the App code handle the new object creation. When ChatEntry creates the new object for the App state, it takes some responsibility for managing those contents. If we want the responsibility of managing the state to live solely with App, we would want it to handle defining the new message object.

This made me think of a related concept in secure design for APIs. Imagine we had an API for creating and updating messages, and it has an endpoint /<msg_id>/like meant to update the true/false liked value. We could have that endpoint accept a body in the request and let the user send an object with data for the message's record (similar to passing a message object from ChatEntry to App), but the user could choose to send any data for those values. If the endpoint only takes in an id and handles updating the liked status for the message itself, there is less opportunity for user error or malicious action.


const heart = props.isLiked ? '❤️' : '🤍';
const senderClass = props.sender === props.localSender ? 'chat-entry local' : 'chat-entry remote';

return (
<div className="chat-entry local">
<h2 className="entry-name">Replace with name of sender</h2>
<div className={senderClass} >

Choose a reason for hiding this comment

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

Another option could be to have an interpolated string here that always holds chat-entry and use a placeholder where we pass only the remote or local class name (so we don't repeat chat-entry anywhere):

const senderClass = (props.sender === 'Vladimir') ? 'local' : 'remote';
...
<div className={`chat-entry ${senderClass}`}>

<h2 className="entry-name">{props.sender}</h2>
<section className="entry-bubble">
<p>Replace with body of ChatEntry</p>
<p className="entry-time">Replace with TimeStamp component</p>
<button className="like">🤍</button>
<p> {props.body} </p>
<p className="entry-time">{<TimeStamp time={props.timeStamp}/> }</p>
<button className="like" onClick={onUpdateButtonClick}>{heart}</button>
</section>
</div>
);
};

ChatEntry.propTypes = {
//Fill with correct proptypes
};
/* ChatEntry.propTypes = {
id: PropTypes.number.isRequired,
sender: PropTypes.string.isRequired,
body: PropTypes.string.isRequired,
timeStamp: PropTypes.string.isRequired,
isLiked: PropTypes.bool.isRequired,
onUpdate: PropTypes.func.isRequired,
localSender: PropTypes.string.isRequired
}; */

export default ChatEntry;
1 change: 1 addition & 0 deletions src/components/ChatLog.css
Original file line number Diff line number Diff line change
Expand Up @@ -2,3 +2,4 @@
margin: auto;
max-width: 50rem;
}

38 changes: 38 additions & 0 deletions src/components/ChatLog.js
Original file line number Diff line number Diff line change
@@ -0,0 +1,38 @@
import React from 'react';
import ChatEntry from './ChatEntry.js';
import PropTypes from 'prop-types';

const ChatLog = (props) => {
const chatEntries = props.entries.map((entry) => (
<ChatEntry
id = {entry.id}
sender = {entry.sender}
timeStamp = {entry.timeStamp}
body = {entry.body}
isLiked = {entry.liked}
onUpdate = {props.onUpdateEntry}
localSender = {props.sender1}
/>

));

return (
<section className="chat-log">
{chatEntries}
</section>
);
};

/* ChatLog.propTypes = {
entries: PropTypes.arrayOf(PropTypes.shape({

Choose a reason for hiding this comment

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

Really nice use of PropTypes.

id: PropTypes.number.isRequired,
sender: PropTypes.string.isRequired,
body: PropTypes.string.isRequired,
timeStamp: PropTypes.string.isRequired,
liked: PropTypes.bool.isRequired
})),
onUpdate: PropTypes.func.isRequired,
sender1: PropTypes.func.isRequired
};
*/
export default ChatLog;