frontend

Code challenge - frontend

This code challenge tests your frontend skills.

Scenario

We really really urgently need a sweet list of your public GitHub Repos, but someone left it half finished! Oh no! Your task is to:

1. Read this README
2. Install deps with yarn or npm install. We usually use yarn.
3. Create a MVP of the repo list (hint: check // @TODO:s)
4. Make sure that the tests pass (yarn test)
5. (If you are applying for a job) Submit your work to us (See ../../README.md) and we will discuss it in the next interview!

MVP

• Can show a initial list of the repositories the user has, including:
  • Link to the repo
  • Name of the repo
  • Description
  • Language
• Can paginate through all the repositories by pressing a Load more button
• Tests pass

The layout

Should look something like this:

There's also a Figma layout for it.

Hints

• This project was bootstrapped with Create React App, so if you are familiar with CRA, you are in luck! Otherwise you might want to get familiar with it first.

• The tests are done with Jest and Enzyme, but you can use plain React TestUtilities or something like react-testing-library too.

• You'll need a GitHub account to get the API token. See settings/tokens.

• The project uses styled-components for the CSS(-in-js), because most of our projects have also used it. Same with redux and redux-thunk, but you can get rid of both or replace them with some other state management system you want to.

• You will find that the project is really incomplete, as in it might actually be completely broken, but that's expected. Debugging is part of the job and ask for help if you get stuck.

• This project uses our styleguide, which might not fit 100% to your current coding style. Not to worry, we are quite flexible with it and formatting is handled by Prettier in pre-commit phase.

Bonus points

We use lots of GraphQL these days, mainly with Apollo. Document how you would do the app if it was using GraphQL. If you are really feeling wild, implement it!

Generic CRA README

Below you will find some information on how to perform common tasks.
You can find the most recent version of the full guide guide here.

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.