- Work in a fork of this repository
- Work in a branch on your fork
- Write all of your code in a directory named
lab-+<your name>e.g.lab-duncan - Submit a pull request to this repository
- Submit a link to your pull request on canvas
- Submit a question, observation, and how long you spent on canvas
- copy your lab-14 or comparable api into into a backend directory
- README.md -- with a documention about your lab
- .babelrc -- with all dependencies and dev-dependencies
- .eslintrc.json -- with the class .eslintrc.json file
- .gitignore -- with a robust gitignore
- .eslintignore -- with the class .eslintignore
- yarn.lock -- with the yarn lockfile
- package.json -- with all dependencies and dev-dependencies
- webpack.config.js -- with webpack config
- src/ -- containing the front end code
- src/main.js -- renders the app
- src/style -- containing your sass
- src/style/main.scss -- for importing and including reset and base
- src/style/_vars.scss -- sass variables
- src/style/_reset.scss -- sass reset
- src/style/_base.scss -- base styles
- src/style/_layout.scss -- layout styles
- Create a frontend for your lab-14-two-resource-api.
- You can also choose to to instead use a comparable RESTful API that does not have auth (must permit full CRUD)
- You are only required to create CRUD opperations for a single resource of your backend
- Use react/redux best practices
- Add validation in your redux routers
- Add reporter and thunk middleware to your redux store
- make async action creators for making ajax request to your backend
- make sync action creators from updating your app store
- Test your redux reducers
- Test your util methods
- Create full crud for two resources
Write a description of the project in your README.md