ntilbe / web-sprint-challenge-advanced-web-applications

Advanced Web Applications Sprint Challenge

Read these instructions carefully. Understand exactly what is expected before starting this Sprint Challenge.

This challenge allows you to practice the concepts and techniques learned over the past sprint and apply them in a concrete project. This sprint explored advanced web applications. During this sprint, you studied React testing, client-side auth, HTTP methods, and Ziet. In your challenge this week, you will demonstrate your mastery of these skills by creating a login page.

This is an individual assessment. All work must be your own. Your challenge score is a measure of your ability to work independently using the material covered through this sprint. You need to demonstrate proficiency in the concepts and objectives introduced and practiced in preceding days.

You are not allowed to collaborate during the sprint challenge. However, you are encouraged to follow the twenty-minute rule and seek support from your TL if you need direction.

You have three hours to complete this challenge. Plan your time accordingly.

Introduction

In this project you will create a login page and request a token from the server that you'll use to send all other requests to the server. You will then be able to fetch the color data array, update data, and delete data, and watch the fun happen!

Note You can use the sites like the following to get color hex codes:

• Color-Hex

Commits

Commit your code regularly and meaningfully. This helps both you (in case you ever need to return to old code for any number of reasons) and your team lead as the evaluate your solution.

Interview Questions

Be prepared to demonstrate your understanding of this week's concepts by answering questions on the following topics. You might prepare by writing down your own answers before hand.

1. Explain what a token is used for.

A token is a unique string of alphanumeric characters that is attached to every request of a users session to authenticate the users access to the app/website.

2. What steps can you take in your web apps to keep your data secure?

Don't store user account information locally, use Tokens instead to give access. Use PrivateRoutes in your application to protect pages from view of unauthorized users.

3. Describe how web servers work.

Web Servers can refer to a computer that stores information for a website, or the program that actually runs on that computer. The computers store the code for different websites. The programs "serve" up the requested project code when someone accesses the site. We can access those servers via the world wide web, we can retrieve the resources and information from that specific server and have it displayed in our browser.

4. Which HTTP methods can be mapped to the CRUD acronym that we use when interfacing with APIs/Servers.

(C)Create = POST, (R)Read = GET, (U)Update = PUT, (D)Delete = DELETE

You are expected to be able to answer questions in these areas. Your responses contribute to your Sprint Challenge grade.

Instructions

Task 1: Project Set Up

• Create a forked copy of this project
• Add your team lead as collaborator on Github
• Clone your OWN version of the repository (Not Lambda's by mistake!)
• Create a new branch: git checkout -b <firstName-lastName>.
• Implement the project on your newly created <firstName-lastName> branch, committing changes regularly
• Push commits: git push origin <firstName-lastName>
• RUN npm install at the root to retrieve all the dependencies for the node server. You will not need to create any react apps here nor will you need to install any other dependencies. You should have all you need in this repo.
• LOOK at all the files you've been given for this project. One important file to note is server.js. This file contains an API that you are going to be interfacing with. Below is documentation on how to interact with the API.
• RUN npm start to get your API up and running on http://localhost:5000. This is the URL you're going to need to use within your React app in order to make AJAX requests for data.
• LOOK at your client directory and notice it's just a plain ol' React App that we've built using create-react-app. cd into client and run npm install to retrieve the client side dependencies.
• RUN npm start to fire up your React application.

Task 2: Project Requirements

Your finished project must include all of the following requirements:

Stage 1 - Authentication

Build a login form to authenticate your users.

• Construct an AXIOS request to retrieve a token from the server. You'll use this token to interact with the API
• Save the token to localStorage
• Build a axiosWithAuth module to create an instance of axios with the authentication header
• Build a PrivateRoute component and use it to protect a route that renders the BubblesPage component

Stage 2 - Consuming the API

• When BubblePages renders, make a GET request to fetch the color data for your bubbles.
• In ColorList.js, complete the saveEdit and deleteColor functions to make AJAX requests to the API to edit/delete data
• Watch and enjoy as your app responds to updates in the data. Check out Bubbles.js to see how this is built.

API Documentation

• [POST] * to /api/login: returns a token to be added to the header of all other requests. Pass in the following credentials as the body of the request: { username: 'Lambda School', password: 'i<3Lambd4' }
• [GET] to /api/colors: returns the list of colors and their hex codes.
• [POST] to /api/colors: creates a new color object. Pass the color as the body of the request (the second argument passed to axios.post).
• [PUT] to /api/colors/:id: updates the color using the id passed as part of the URL. Send the color object with the updated information as the body of the request (the second argument passed to axios.put).
• [DELETE] to /api/colors/123: removes the color using the id passed as part of the URL (123 in example).

Stage 3 Testing

• Finish the test in BubblePage.test.js to test that your app is fetching the bubble data from the API

In your solution, it is essential that you follow best practices and produce clean and professional results. You will be scored on your adherence to proper code style and good organization. Schedule time to review, refine, and assess your work and perform basic professional polishing including spell-checking and grammar-checking on your work. It is better to submit a challenge that meets MVP than one that attempts too much and does not.

Task 3: Stretch Goals

After finishing your required elements, you can push your work further. These goals may or may not be things you have learned in this module but they build on the material you just studied. Time allowing, stretch your limits and see if you can deliver on the following optional goals:

• Build out another form to add a new color to your color list
• Build a custom hook called useApi that you can use to make all of your API calls
• Add more tests to give you further confidence in the code you're shipping

Submission format

Follow these steps for completing your project.

• Submit a Pull-Request to merge Branch into master (student's Repo). Please don't merge your own pull request
• Add your team lead as a reviewer on the pull-request
• Your team lead will count the project as complete after receiving your pull-request