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
Orion signup flow rework #321
base: master
Are you sure you want to change the base?
Orion signup flow rework #321
Conversation
id: ID! | ||
|
||
"Membership associated with the blockchain account (controllerAccount)" | ||
memberships: [Membership!] @derivedFrom(field: "controllerAccount") |
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.
Should we support multiple memberships within Atlas? Seems, like an overkill. Besides that it is possible from runtime perspective, it will only complicate the membership dropdown (we already had some feedback that it is complicated @dmtrjsg)
{ joystreamAccountId: payload.joystreamAccountId } | ||
) | ||
|
||
console.log('after update') |
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.
log
}) | ||
|
||
// Mark the token as used | ||
token.expiry = new Date() |
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't we just drop the token if used?
75160c2
to
2fba0a5
Compare
6f8a7d0
to
d580268
Compare
Addresses #320