React Coding Challenge

The task

Your job is to create a SPA which stores file details in the browsers local storage and keeps a history. The files are not uploaded to any service. Only the file meta deta is stored in the browser storage.

Tech stack:

React: Create react app starter
State Managment: Redux
Styled Components: (if you like to style things): Styled Components

Screens:

Main Screen
- Displays an upload dialog
- Once a file was dropped on the file upload dialog area it will dispaly the file name and a "Save File" and "Reset File" button
- Only PDF, DOCX, DOC are allowed
- Clicking "Save File" will persist the file meta data in the browsers local storage
- Clicking "Reset File" will reset the upload dialog
- List all previously saved files (if any) in a table
- Clicking on the "X" icon in the file list will remove the item and remove it from the browser storage
- The table contains filename, file size (in bytes, kilobytes, megabytes, gigabytes, terabytes) and the file format (extension without the dot)

Must-have:

React, Redux
Validation on forms
Usage of modern js functionality (ES6+)
Pull Request to to this repo once the task is completed

Good to have:

Typescript
Clean code (linters, prettier)
Tests
App deployed to Vercel

What will we be paying attention to:

How you split code for components
How your store looks like and how you communicate with redux.
Reusability of the components.
Code repetitions and reusability (keep your code DRY and simple KISS).
How and where you put your business logic.
Code optimization and the solution's performance.
Working in accordance with good practices in general.
How you communicate with the browser storage API.
Handling unexpected errors or potential exceptions.

Getting Started with this challenge

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.

rico-et22/react-coding-challenge

React Coding Challenge

The task

Tech stack:

Screens:

Must-have:

Good to have:

What will we be paying attention to:

Getting Started with this challenge

Available Scripts

yarn start

yarn test

yarn build

yarn eject

Learn More

Code Splitting

Analyzing the Bundle Size

Making a Progressive Web App

Advanced Configuration

Deployment

yarn build fails to minify

`yarn start`

`yarn test`

`yarn build`

`yarn eject`

`yarn build` fails to minify