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.
The project implements a simple UI that is enabled to fetch users data from an API and update the status of each user. I used the packages
The project logic is contained in 3 main directories
- components
- actions
- reducers
The first directory holds the custom components we used. These are a Table Header, a User Item (aka the row in our table) representing a specific user, a User List which contains the body of the table and finally a User Table element which combines all the elements mentione above and it is the one finally rendered in the element.
The typical Actions / Reducers / Store form has been kept for redux functionality.
UserActions.js holds the actions that can be done for a user and it represents the API communication level
UserReducer.js holds the state change logic