- Becca Burns
- Alex Saxena
- Front End: React v.16.10.2, Semantic UI, CSS
- Back End: Rails 5.2.3
- Testing frameworks: Cypress, Enzyme
- Deployed at: Netlify and Heroku.
This repository contains our solution to the client side of the Cooper Challenge. Our respective repositories for the Cooper API built in Rails can be found here.
- Yarn
- React
- Enzyme
- Cypress
- Semantic UI for React
- Axios
- Chart.js
- react-chartjs-2
To test this application you need to fork it to your own GitHub account and clone it to your local workspace.
$ yarn install
$ yarn test
$ yarn run cy:open
$ yarn start
To be able to fully appreciate the software, one can log into the app with the following test-credentials:
- Email: [email protected]
- Password: password
Later on, we would like to: Finish implementing the BMI calculator on the client side and add the save data functionality to it.
This project is released under the MIT-license.
Thank you CraftAcademy for giving us this assignment.
In this project the calculation is performed on the client-side.
What are the pros and cons of client-side processing/calculation ? Pros
- It can, under some circumstances, mean more processing power.
- It makes scaling easier because computational load is not increased with each new user.
- Only increases storage but does not increase computational load on server. Hence, less server-cost. Cons
- Security, some processing should never be done client-side (banking f.ex.).
- Client-side resources can be more of an issue, f.ex. hardware capabilities and software compatibility on client-side.
- Software (calculations) can not be written in any language or framework.
- With server-side computation, more of the debugging is focused on a single target rather than, possibly, multiple client-side scenarios.