Add one wallet endpoints

[fuzzyami]

No description provided.

[oryband]

1. this isn't python world and no one is using underscore naming
2. if you can, use a single action word instead of two or more
3. search for RESTful API endpoint naming convention and pick something that makes sense

[fuzzyami]

The current horizon version uses underscore in an endpoint. if they can, surely we can too. refer to https://github.com/stellar/go/blob/009e6e45c9f514e8e4f102461fbaefdf92b4f448/services/horizon/internal/web.go#L179

[oryband]

there's also account_id used in Horizon responses. Check the difference and keep it consistent with the rest of the responses Horizon does.

[fuzzyami]

from what I gather, "id" is used to identify the page returned. in some cases, its the account id but in others, it might a tx hash or another identifier for the page. In other words, I'll need to use account_id instead of id.

[oryband]

possible account_id needed?

[oryband]

if Action is a struct, use a pointer. if it's an interface it's ok

[fuzzyami]

its done exactly this way in all the other actions.

[oryband]

break lines here like in the above functions

[oryband]

when working with xdr. objects, do you need to work with copies or references?

[fuzzyami]

AFAIK, copies.

[oryband]

Test scenarios that we should test:

1. master account which doesn't exist - test both endpoints
2. master account which isn't linked to any other account - "
3. matser account which is linked to another account - "
4. matser account which is linked to two other accounts - "
5. matser account which is linked to three other accounts - "
6. test mass linking: you can use table test with the last three tests are, and test for linking 100+ accounts to a master account

edge cases:

1. account A linked to B, which also links back to A - test all endpoints
2. account A linked to B, account B linked to C - " + verify that A only shows B
3. cyclical: account A linked to B, B linked to C, C linked to A - " + verify A only shows B
4. repeat 1-3 but have A link to 3 normal accounts, and B as well to other 3 normal accounts. this is a "merge" of all test scenarios mention above this line.

[oryband]

should you use a pointer in the type here? verify with other implementations that already exist in the codebase

[oryband]

standard in go is to put comments on top of code, not side by side

[oryband]

i would let @doodyparizada look at the queries as well