-
Notifications
You must be signed in to change notification settings - Fork 19
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
Allow claim action for every logged in person #2650
Conversation
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.
It's working as expected! Good work
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.
Other than change I pointed out, this is good to go
@@ -136,7 +126,7 @@ const UnclaimedTransfersItem = ({ | |||
error={ActionTypes.COLONY_CLAIM_TOKEN_ERROR} | |||
success={ActionTypes.COLONY_CLAIM_TOKEN_SUCCESS} | |||
transform={transform} | |||
disabled={!userHasPermission || !isNetworkAllowed} | |||
disabled={!isNetworkAllowed || ethereal} |
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.
So this needs to check if the user has a registered profile as well, not just that it's not an ethereal wallet.
Something like this:
const { walletAddress, username, ethereal } = useLoggedInUser();
const hasRegisteredProfile = !!username && !ethereal;
This is not necessarily something in the contracts, but it something we don't allow in the dapp, if you don't have your profile registered first.
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.
Good job!
82a017d
to
3609e79
Compare
3609e79
to
a7d3cd2
Compare
Description
This PR updates logic for claim button.
Resolves #2647