Can we get rid of the /apps section? #4

Activity

1. jcnelson commented on Dec 8, 2016

   

   jcnelson

   on Dec 8, 2016

   More actions

   I can get behind making /resources its own top-level route.

   I'm not sure I agree with making /stores a top-level collection. I see the "root" of an application's state as a user, which has a datastore, a keypair, a default session lifetime, a set of API method calls the user can make, and so on as properties. We can stop giving stores a separate :storeID, however, if you want there to be a 1-to-1 correspondence with users (in doing so, we'd also drop the methods for creating and deleting stores, since that would happen as part of creating and deleting the user).
2. shea256 commented on Dec 8, 2016

   

   shea256

   on Dec 8, 2016

   ContributorAuthor

   More actions

   Oh I don't mean we should make /stores a top-level collection.

   I actually meant that "Get all app accounts" (GET /users/{userID}/app) can be replaced with "Get all stores".
3. shea256 commented on Dec 8, 2016

   

   shea256

   on Dec 8, 2016

   ContributorAuthor

   More actions

   We can stop giving stores a separate :storeID, however, if you want there to be a 1-to-1 correspondence with users (in doing so, we'd also drop the methods for creating and deleting stores, since that would happen as part of creating and deleting the user).

   Yes I like this. Each app-user-pair would be unique and this would be reflected in the path, which has both the user ID and the app ID.