Open 0xCLARITY opened 4 years ago
It may make sense for the private API to expose nested resources under user.
For example, GET /v1/users/$xpring.money/hbergren/addresses/xrpl-testnet
GET /v1/users/$xpring.money/hbergren/addresses/xrpl-testnet
Then you could imagine the following "helper methods":
POST /v1/users/$xpring.money/hbergren/addresses/
PUT /v1/users/$xpring.money/hbergren/addresses/xrpl-testnet
PATCH /v1/users/$xpring.money/hbergren/addresses/xrpl-testnet
DELETE /v1/users/$xpring.money/hbergren/addresses/xrpl-testnet
This is probably related to #142 (implementing PATCH for the private API), and maybe even #141.
This sounds like something GraphQL could do quite well.
It may make sense for the private API to expose nested resources under user.
For example,
GET /v1/users/$xpring.money/hbergren/addresses/xrpl-testnet
Then you could imagine the following "helper methods":
POST /v1/users/$xpring.money/hbergren/addresses/
PUT /v1/users/$xpring.money/hbergren/addresses/xrpl-testnet
PATCH /v1/users/$xpring.money/hbergren/addresses/xrpl-testnet
DELETE /v1/users/$xpring.money/hbergren/addresses/xrpl-testnet
This is probably related to #142 (implementing PATCH for the private API), and maybe even #141.