Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for manage multiple nodes #71

Closed
tmm360 opened this issue Apr 21, 2021 · 2 comments
Closed

Add support for manage multiple nodes #71

tmm360 opened this issue Apr 21, 2021 · 2 comments
Labels
dif:hard Having worked on the specific codebase is important kind:architecture Core architecture of project type:issue

Comments

@tmm360
Copy link
Contributor

tmm360 commented Apr 21, 2021

Currently only a single node is supported at time. This would be required also for #58

@vojtechsimetka
Copy link
Contributor

Thanks @tmm360 this is an issue I wanted to make as well. The idea would be to have a state provider for each Bee node (#40 is the first step) and as an input into this context provider you could have the API and debug API url's.

As for #58, this button is per one node so it can even be implemented now. Simple filter on accounting.filter(r => r.uncashed.toBigNumber.isGreaterThan(0)) gives you list of all peers which have some uncashed balance. Then the Cash all button just triggers cashout on each one of these peers.

Accounting type:

interface UseAccountingHook {
isLoading: boolean
isLoadingUncashed: boolean
error: Error | null
totalsent: Token
totalreceived: Token
accounting: Accounting[] | null
}
export interface Accounting {
peer: string
uncashedAmount: Token
balance: Token
received: Token
sent: Token
total: Token
}

accounting array: https://github.com/ethersphere/bee-dashboard/blob/master/src/pages/accounting/index.tsx#L37

@vojtechsimetka vojtechsimetka added dif:hard Having worked on the specific codebase is important kind:architecture Core architecture of project labels Apr 23, 2021
@vojtechsimetka
Copy link
Contributor

closing in favour of #135 which is slightly clearer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dif:hard Having worked on the specific codebase is important kind:architecture Core architecture of project type:issue
Projects
None yet
Development

No branches or pull requests

2 participants