- This is our week one code review for the React portion of our course. The goal of this review is to take a previous project we made in angular and clone a static version that includes client-side routing, styling with css objects/modules, propTypes, and components for modular UI elements.
- Successfully implemented Client-Side routing.
- Successfully styled with CSS objects and modules.
- Successfully used propTypes and JSX Looping.
- Created modular components for a slightly modular UI.
- To view project code, clone repository from https://github.com/seanulus/tap-room-react
- Install Node.js
- Open terminal, navigate to project root directory and run npm install.
Run npm run start for a dev server. Navigate to http://localhost:8080/. The app will automatically reload if you change any of the source files.
-
The only issues I ran into doing this project were pretty basic syntax issues. At one point, I incorrectly labelled one of my components but the linter makes it pretty easy to track those problems down. Overall, the process went fairly smoothly.
-
Comparing Angular and React, I like React in this context so far. The functional nature of the library makes it easy for me to visualize what each individual part is doing, especially since the styling, template and coded portions are all present in the same component. It was a lot easier for me to get lost in the component structure of Angular seeing as each component had it's own individual template, style, and coded files to work with. Overall, React seems to make this process a little easier to visualize.
- One console error for deprecated propTypes in React Library. Should not effect performance as of this writing.
- HTML
- CSS
- React
- Javascript
To get more help on the Angular CLI use ng help or go check out the Angular CLI README.
- MIT
Sean McDermott © 2018