-
Notifications
You must be signed in to change notification settings - Fork 3
feat: Human Proof Section #489
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
base: master
Are you sure you want to change the base?
Conversation
tipogi
left a comment
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 missing points, passing to @MiguelMedeiros the UI review of the draft
| const requestLightningInvoice = React.useCallback(async () => { | ||
| try { | ||
| setIsLoading(true); | ||
| const invoice = await Homegate.requestLightningInvoice(); |
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.
Homegate is a service as you define but the organisms does not have access to the services. The only way to access to the services is through, controller and after application. So we are missing, a homegate controller and application. In that case, you will call to HomegateController.requestLightningInvoice().
| const codeValue = code.join(''); | ||
| try { | ||
| setIsVerifyingCode(true); | ||
| const result = await Homegate.verifySmsCode(phoneNumber, codeValue); |
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.
Same as the above code. HomegateController.verifySmsCode()
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.
This is a molecule, it does not have any interaction with data layer or/and external services. It is just an static component
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.
Leaving this open as we might need to add more logic there. US users might not be able to use LN payments.
| } | ||
|
|
||
| // Create new fetch promise | ||
| cachePromise = getSatoshiUsdRate() |
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.
The same reason as above, it has to access through the controller. I would add in the HomegateController another method to get that rate. The function should be renamed to fetchSatoshiUsdRate. The get prefix means that we get data from indexdb
| // Ignore if unmounted or superseded | ||
| if (activeRequestRef.current !== requestId || !isMountedRef.current) return; | ||
| try { | ||
| // TODO: Instead of going to the feed, this should go to the create profile page. |
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.
The merged PR already solves that one. If we signUp/signIn with the QR using ring, and that key does not signup in the app (it has to have profile.json file in the homeserver), we redirect to the creation of the profile.json
tipogi
left a comment
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.
nice UX! for my side, ready the core layer
Adds