Andrea Reginato

Is there any plan to add it? I like the component, but without Typescript support many people are not able to use it. I would love to help in this,...

See also this addon for heroku as inspiration or try to use it.

These days I don't have the needed amount of time to work on making the seed. I think we should find the simplest path to create them. The first idea...

**NOTE** when inviting somebody giving some access levels for some devices they never must be able to access to the secret. This means that is mandatory to not let a...

**NOTE** Only the resource owner or the device creator can deactivate a product. Remember that when a device is deactivated it can be accessed by everyone who knows the `activation...

**NOTE** The invitation API does not look so easy, mainly because we have to be really careful on the fact that a user can own a device initially and then...

**NOTE** checkout also this problem when somebody else create a resource bound to your owned resources. https://github.com/lelylan/devices/issues/9#issuecomment-10856090

**NOTE** Also take good care on removing all invitation tokens when you deactivate a device that is then owned by somebody else.

**NOTE** Right now the /devices/:id/accesses service issue a token that is valid for a specific resource. When the invitation system is done, we must be able to replace the existing...

**NOTE** Think at how invitation service should be made up ``` /invitations /invitations?type=request /invitations?type=received /invitations?status=accepted /invitations?status=rejected /invitations?status=rejected ``` And the structure should have those fields ``` type # on creation...