Included is a working comment app that fetches from an external API and allows the user to add a comment. I have structured the app where app.js handles all data fetching and passing props to components. The initial comments are loaded from an external API, same mock comments. The API call is made with Axios and kept simple as possible. The data is stored in redux slice and then passed to components. I wasn't sure on what the requirements were for input fields and none were given so there is only a simple error check on string length.
-Slices/comment.js contain the selectors for getting the Top 3 Commenters. -There are 2 new components created CommentList and CommenterList. -The Material UI theme is using orange as primary and purple as secondary
As a user, I would like to be able to read a list of comments, add a comment, and see a list of the top 3 commenters.
Please add comments to help explain decisions and add a summary to the README
- Use Material-UI theme for custom color scheme(primary and secondary colors)
- Display list of comments
- Comment UI should consist of avatar(first initial or first + last initial), name, and comment
store/api
has mock comments- Extra: fetch from API to display initial comments instead of mock comments
- Facilitate adding a comment via modal with input fields(name and comment), and submit button
- Display a list of top 3 commenters
- Ui should consist of avatar(same as above) name, and comment count
- Should be listed in descending order of comment count
This project was bootstrapped with Create React App.
In the project directory, you can run:
Runs the app in the development mode.
Open http://localhost:3000 to view it in the browser.
The page will reload if you make edits.
You will also see any lint errors in the console.
Launches the test runner in the interactive watch mode.
See the section about running tests for more information.
Builds the app for production to the build
folder.
It correctly bundles React in production mode and optimizes the build for the best performance.
The build is minified and the filenames include the hashes.
Your app is ready to be deployed!
See the section about deployment for more information.
Note: this is a one-way operation. Once you eject
, you can’t go back!
If you aren’t satisfied with the build tool and configuration choices, you can eject
at any time. This command will remove the single build dependency from your project.
Instead, it will copy all the configuration files and the transitive dependencies (webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except eject
will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.
You don’t have to ever use eject
. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.
You can learn more in the Create React App documentation.
To learn React, check out the React documentation.
This section has moved here: https://facebook.github.io/create-react-app/docs/code-splitting
This section has moved here: https://facebook.github.io/create-react-app/docs/analyzing-the-bundle-size
This section has moved here: https://facebook.github.io/create-react-app/docs/making-a-progressive-web-app
This section has moved here: https://facebook.github.io/create-react-app/docs/advanced-configuration
This section has moved here: https://facebook.github.io/create-react-app/docs/deployment
This section has moved here: https://facebook.github.io/create-react-app/docs/troubleshooting#npm-run-build-fails-to-minify