/kanban-board

Primary LanguageTypeScript

Disclaimer

repo is not forked so there won't be any sneaky peekers in the future

Considerations before diving in

This challenge does not consider as big factors:

  • nice and responsive UI
  • full test coverage
  • tools setup for development process (prettier, eslint, husky, volta, etc)
  • usage of really helpful libraries (components library, forms management library, etc)
  • performance considerations (memoization and virtualization)
  • no CI/CD for running tests or deploying on a pipeline

So what is this up to?

If things mentioned above are not included, what's the deal with this project? Well, here it is:

  • this is my most basic way of doing and working around things
  • expect overall code to be simple and easy to read, follow and enhance, because we all love simple and stupid solutions
  • it's prepared to scale by having a clear structure, focusing mostly on pages and components
  • critical performance components are ready to be memoized and virtualized (dealing with 1000x tasks per list)
  • only one integration test that give us the most confidence our app is working correctly, and sets nice guidance for future devs and tests
  • components folder has only reusable components. TaskForm, Listand Board would just live in the ChallengePage. But we could extract them in the future.
  • removed the package-lock.json since we are using yarn and we don't want other devs to be confused about this.

Video Intro

https://www.loom.com/share/3df7fcb5424644638b00724cb178e2ff

Getting Started with the Every.io engineering challenge.

Thanks for taking the time to complete the Every.io code challenge. Don't worry, it's not too hard, and please do not spend more than an hour or two. We know you have lots of these to do, and it can be very time consuming. If you feel like adding fancy animations, or getting all hip and fresh with the design, go ahead, but it won't earn you any extra points.

The biggest factor will be your code:

  1. How readable, is your code.
  2. How did you organize your components.
  3. Are there any bugs.

Requirements

See the prototype for an example.

You will be creating a basic todo list, with the following functionality.

  1. The list has 3 states. Each represented by a column. Similar to Trello.
    1. Todo
    2. In Progress
    3. Done
  2. Each list item has a right and left arrow button.
    1. The right arrow moves the list item from:
      1. Todo to In Progress
      2. In Progress to Done
    2. The Left arrow moves the list item from
      1. Done to In Progress
      2. In Progress to Todo
  3. If the list in the in the Todo column, the left button should be disabled
  4. If the list is in the Done column, the right button should be disabled.
  5. There should be form with a text input below the buttons. When the user submits the form, the text from the text input should be added to a new todo item in the Todo column.

Quick Start

  1. npm install
  2. npm run start
  3. open your browser to http://localhost:3000
  4. Delete the h2 from the component in src/ChallengeComponent.tsx
  5. Add your code to that component.

Original CRA README below

Getting Started with Create React App

This project was bootstrapped with Create React App.

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.

Learn More

You can learn more in the Create React App documentation.

To learn React, check out the React documentation.