This repository has been archived by the owner on Mar 8, 2024. It is now read-only.

Maybe: Expose nested subresources under user? #171

Open

0xCLARITY opened this issue Mar 27, 2020 · 1 comment

Labels

API: Private CRUD Enhancement

Collaborator

0xCLARITY commented Mar 27, 2020

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.

The text was updated successfully, but these errors were encountered:

0xCLARITY added the Enhancement label

Member

dino-rodriguez commented Apr 2, 2020 •

edited

Loading

This sounds like something GraphQL could do quite well.

0xCLARITY added the API: Private CRUD label

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.