Skip to content

akashrajum7/github-react-fork-list

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

17 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Github-React-Fork-List

⚠️ DO NOT DEPLOY THIS APP TO A PUBLIC URL ⚠️

Since this is a frontend application, all the API key's are exposed to anyone visiting the website, so please avoid making this app publicly available

Application developed as part of a requirement for Interview for the position of a Full Stack developer at The Live Green Co.

To-Do's

  • Obtain the users who have forked the React repo (https://github.com/facebook/react/) using the GitHub API.
  • Paginate.
  • Displays the list of users who have forked the repo in a list with card layout.
  • Include a "follow" button, On clicking the follow button, using my API key set in a config file, I should be able to follow that user.
  • Write a README on the process to configure and use your application
  • Please include good commit messages to explain the development process and approach continuously as you develop the project

This project was bootstrapped with Create React App.

Setup

  • Rename .env.format to .env.development and please get your API key from here and place your key in the file.

Available Scripts

In the project directory, you can run:

npm start

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.

npm test

Launches the test runner in the interactive watch mode.
See the section about running tests for more information.

npm run build

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.

npm run eject

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.

Learn More

You can learn more in the Create React App documentation.

To learn React, check out the React documentation.

Code Splitting

This section has moved here: https://facebook.github.io/create-react-app/docs/code-splitting

Analyzing the Bundle Size

This section has moved here: https://facebook.github.io/create-react-app/docs/analyzing-the-bundle-size

Making a Progressive Web App

This section has moved here: https://facebook.github.io/create-react-app/docs/making-a-progressive-web-app

Advanced Configuration

This section has moved here: https://facebook.github.io/create-react-app/docs/advanced-configuration

Deployment

This section has moved here: https://facebook.github.io/create-react-app/docs/deployment

npm run build fails to minify

This section has moved here: https://facebook.github.io/create-react-app/docs/troubleshooting#npm-run-build-fails-to-minify

About

Application developed as part of a requirement for Interview for the position of a Full Stack developer at The Live Green Co.

Resources

Stars

Watchers

Forks