Skip to content

README.md

Latest commit

 

History

History
45 lines (26 loc) · 2.48 KB

README.md

File metadata and controls

45 lines (26 loc) · 2.48 KB

Septa Regional Rail Fares Calculator

Live site: https://rng-septa-fare-calc.netlify.app

Tech stack used: Javascript, ReactJS, and Typescript Total Time Spent: 3hr-30min

The way I approached this project was to build out the scaffolding and most of styling first to get the look and feel of the components down. I took a look at which components could be reused in places and created generic components for them. Using typescript allowed me to nail down and define the types for my component props and also the actual data I expect to receive. Throughout the coding process, I tried to write clean and optimized code; readable and easy to digest; leaving no guess work (at least I hope)

If I had more time, I would work on maybe some unit tests and look into mobile to desktop responsiveness.

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.