Skip to content

ninetydays/coding-challenge-frontend

Repository files navigation

Kross Finance Coding challenge

Hi, thanks for applying for the react front-end developer position at Kross Finance Korea. This coding challenge is aiming to evaluate a candidate's problem-solving skills in real-world experiences. The specific tasks are listed in the Github issue tracker and you could submit and merge a PR as you might work with the GitHub issue tracker. The tasks include a bug fix and feature request.

Before you start

  • This README file has a basic description of the project. Please read it carefully.
  • Look through the tasks and give a quick time estimation for completing the challenge.
  • Submit the PR and merge by yourself for each task. Make sure to specify how much time you spent on the task.
  • use yarn over npm

Install

  1. Make sure you have node, yarn installed.
  2. install dependencies
$ yarn install
  1. running test to check everything is fine
$ yarn test
  1. runnging development server
$ yarn start

Available Scripts

In the project directory, you can run:

yarn 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.

yarn test

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

yarn 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.

yarn 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.

About

No description, website, or topics provided.

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published