Brett Andrews

Working example: ```js import aws4 from 'aws4' import mqtt from 'mqtt' const AWS_IOT_ENDPOINT = 'YOUR_ENDPOINT_ID.iot.us-east-1.amazonaws.com' function signRequest ({ region, accessKeyId, secretAccessKey }) { return aws4.sign({ host: AWS_IOT_ENDPOINT, path: '/mqtt', service:...

Sorry, I should have been more clear. The `create` method would fail if the partition key exists (i.e it shouldn't update). I get being consistent with the DynamoDB API, but...

Compare that to: ``` Entity.create({ identifier, name }) ``` Or, if we must: ``` Entity.put({ identifier, name }, { createOnly: true }) ``` This is pretty low-level: ``` { conditions:...

What did you have in mind to make this really clear? Is it enough to highlight this in the docs? Or did you want to scope these to something like...

I'm using Dynalite with https://www.npmjs.com/package/jest-dynalite. Not sure if that's taking care of the `setTimeout` stuff for me, but I haven't hit an issue with the table not being ready.

Keenly anticipating the release :)

I'd advise against using aliases. This is how I see those two routes: ``` /student/:studentId/course/:courseIds (note that I would allow :courseIds to be a comma delimited list of ids) GET:...

I totally understand putting the multiple id approach on hold, so we will move forward assuming `:courseId` is a single numeric value. I have a couple of issues. | `POST...

@ackerdev those mostly look fine for one-to-many relationships (one magazine has many ads), but certainly don't work for many-to-many (many students have many courses example we were using previously). Furthermore,...

> I assume you mean that you can't associate or dis-associate many-to-many relations Correct. My approach would be to use the same routes and methods for both one-to-many and many-to-many,...