-
Notifications
You must be signed in to change notification settings - Fork 49
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: added person credential loading screen #2094
Conversation
Signed-off-by: wadeking98 <wkingnumber2@gmail.com>
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.
Some thoughts on dependencies in the useEffect
. LMK if I'm misunderstanding the docs I ref in the first comment.
@@ -0,0 +1,53 @@ | |||
import { useTheme } from '@hyperledger/aries-bifold-core' |
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.
Curious if there was a component in Bifold that could just be modified to take in a different graphic?
setDidCompleteAttestationProofRequest(true) | ||
} | ||
}, attestationProofRequestWaitTimeout) | ||
}, [remoteAgentDetails]) |
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.
}, [remoteAgentDetails]) | |
}, [remoteAgentDetails, receivedProofRequests, attestationProofRequestWaitTimeout, logger]); |
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.
attestationProofRequestWaitTimeout and logger should be constant for the duration of the screen no? I don't think its possible for either of them to change without reloading the app
return () => { | ||
subscriptions.forEach((subscription) => subscription.remove()) | ||
} | ||
}, []) |
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 in this one you may need:
- The navigation object is included in the dependencies array to ensure that the effect re-runs if navigation changes.
- DeviceEventEmitter, BifoldEventTypes, or AttestationEventTypes are constants and do not change, they don't need to be in the dependencies array. If they can change, they should be added to the array as well.
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.
Not quite sure what you mean with adding the navigation object to the dependancy array. The navigation object should only change when we trigger a navigation event like navigating to a new screen, in which case we wouldn't want to re-run the useEffect because we'd be leaving this screen right?
goToCredentialOffer(credential.id) | ||
} | ||
} | ||
}, [receivedCredentialOffers, remoteAgentDetails]) |
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.
store
?
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.
maybe store.developer.environment.iasPortalUrl so we're not reacting to every change that happens on the store object? IMHO iasPortalUrl shouldn't be changing while we're on this screen so should we even just treat it as a constant?
Signed-off-by: wadeking98 <wkingnumber2@gmail.com>
a1a393c
to
2edf41d
Compare
Quality Gate passedIssues Measures |
Added loading screen to person credential flow instead of button activity indicator
personLoading.mp4