mfarukkoc / kloia-case-study Goto Github PK

This project was bootstrapped with Create React App, using the Redux and Redux Toolkit template.

It is a case study at the end of the kloia React Bootcamp.

• As a user, I should be able to view coffees available within the system.
• As a user, I should be able to view coffee categories available within the system.
• As a user, I should be able to filter coffees with a free-form text input.
• As a user, I should be able to choose a coffee category to filter visible coffees

├─── public
├─── src
├────── app : App component and Redux store definitions
├────── assets
└───────── fonts : font resources
├────── components : pure components used in many places
├────── redux : Redux reducer definitions
├────── @fake-db : fake db services
└────── pages : Page components

Requirements

• node v14.17.3
• npm 6.14.10 or yarn 1.22.11

Install required packages by

yarn or npm install

Then start development server by

yarn start or npm run start

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.

Run the ESLint linting task.

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.