Skip to content

codefellows-seattle-javascript-401n5/34-asynchronous-actions

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

3 Commits
 
 
 
 

Repository files navigation

cf Async Actions

Submission Instructions

  • 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

Requirements

Configuration

backend/
  • copy your lab-14 or comparable api into into a backend directory
frontend/
  • Follow standard conventions, see previous labs for reference.

Feature Tasks

  • Create a frontend for your lab-14-two-resource-api or week 5 project
  • You can also choose to use a comparable RESTful api that does not have auth (must permit full CRUD)
  • You are only required to create CRUD operations for a single resource of your backend
  • Use react/redux best practices
  • Add validation in your redux routes
  • 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

  • Test your redux reducers
  • Test your util methods (if any)

Stretch Goals

  • Create full crud for two resources

Documentation

Write a description of the project in your README.md, including detailed instructions for how to build your app. In your frontend README.md add a code block with your frontend .env vars, and in your backend README.md add a code block with your backend .env vars.

About

Lab 34 - Asynchronous actions

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published