This app runs live on https://konn-test.netlify.app/
In the coding process, the following design patterns have been used:
- Separation between Container and Presentational Components
- Flux architecture for the state management
- SOLID principles modified accordingly for functions
- Separation of concerns in every level (module function etc)
Proper error handling was performed. Fallback route was included to handle invalid URLs. Proper messages are shown on the UI, in case of rejected API call, and, in case of fulfilled API call, if there are empty response.
The project is standing in two pillars:
- UI
- Logic
The app consumes the github api. To establish a pattern here, I chose to use the github home page color pallette and a relevant image. When the user clicks on a follower or repo link, it links to the proper github page.
The app follows the design patterns specified in Design patterns. Furthermore, I use proper established libraries for state management, API callsand CSS, that allow scalability of the app and readability of the code.
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.