-
Notifications
You must be signed in to change notification settings - Fork 89
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
feat(frontend): manage incoming auth tokens #2935
base: main
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for brilliant-pasca-3e80ec canceled.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for the contribution! A few first comments
62ece89
to
0a1bdbf
Compare
Co-authored-by: Max Kurapov <[email protected]>
…uthTokens` as `string[]`
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we also handle the case when overflowing?
Also, I will tag this as hacktoberfest
! See more here
@@ -122,6 +122,9 @@ export const peerToGraphql = (peer: Peer): SchemaPeer => ({ | |||
id: peer.id, | |||
maxPacketAmount: peer.maxPacketAmount, | |||
http: peer.http, | |||
incomingTokens: peer.incomingTokens?.map( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think incomingTokens
would probably benefit from a separate resolver kind of like liquidity
is done. Check packages/backend/src/graphql/resolvers/index.ts
. This will require a new function in the HttpTokenService
instead of doing .withGraphFetched('incomingTokens')
in the getter in peer service.
Changes proposed in this pull request
Context
fixes #2765
Checklist
fixes #number