PATCH request on /user

[Daeluse]

Sending a PATCH request to /users/id with parameters results in XMLHttpRequest cannot load http://104.131.175.67:3000/users/3. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://localhost:3000' is therefore not allowed access. The response had HTTP status code 500.

[Daeluse]

Ideally, this route would be capable accepting the following optional parameters

• first_name
• last_name
• email
• password
• avatar(TBD)

If password is set, it should be hashed before it is stored. If avatar is set, the image should be uploaded to S3 and the url should be stored. See #19 for how this is handled.

[bradcypert]

Just a heads up, we're saving the avatar_url as pic_url. There's no reason to send the picture to the backend and then to S3 when we can just send it to S3 from the frontend and pass the url to the backend.

Can pass in any of the following: first_name last_name age pic_url pass

We update based off the ID in the route.