ga-wdi-boston / upload-client Goto Github PK

Trying to think of creative ways to cut this talk down, and I wonder if creating an echo server instead of using httpbin might be a better/more effective transition state?
i.e. instead of using POST httpbin you POST to localhost, and your create function in the uploads controller, it just says:

res.json({ body: req.body })

or something like that.

"npm run bin/upload-aws [comment]"

should be

"npm run upload-aws [comment]"

I'm not sure what @payne-chris-r wanted here, so hopefully he can illuminate.

Is this to long?

Once you save the express-template as express-multer-api, the instructions on installation in the express template says rename all instances of express-template to name of app.

Make clear that this should match express-multer-api

Great finds @nlkassad

• http://docs.aws.amazon.com/AmazonS3/latest/dev/acl-using-java-sdk.html
• http://docs.aws.amazon.com/AmazonS3/latest/API/RESTBucketGETacl.html

In the Objectives section the mention "Create path names" is unclear. As a reference to file path it should have additional context.

@gaand

• @gaand

This would be a more realistic solution.

from express-template to express-api-template via @gaand

In node package file-type sentence.

@gaand

• @gaand

(Based on template naming conventions)

There is certainly value to "building a whole feature" in one go. However, it's also clear that by the end of a 9 hour code-along, the developers are fried. My concern is by the end they don't care and are just making sure they write what we write and not thinking about WHY. I sprinkled in why did I just write what I just wrote?s and what does this code do?s and if I change this '(data)' to '(blah)' what else do I have to change in order for my code to still work?s, but I'm still concerned there is a severe lack of understanding and more of a 'going through the motions'. Not sure how to resolve or if it's even possible...

No JavaScript.

Add file to this repo?