-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
[No QA] Add BeneficialOwnersStep (UI Only) #3585
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.
@@ -304,6 +304,19 @@ export default { | |||
noPhoneNumber: 'Por favor escribe un número de teléfono que incluya el código de país e.g +447814266907', | |||
maxParticipantsReached: 'Has llegado al número máximo de participantes para un grupo.', | |||
}, | |||
beneficialOwnersStep: { |
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 occurred to me that I forgot to add the requestorStep values to this file 🙈
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.
Why was this left in english if this is the spanish file?
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 we are fixing that here https://expensify.slack.com/archives/C21FRDWCV/p1629825626117900
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.
When we started this there was pressure to get it finished within 2 weeks so we moved very quickly and Spanish translations were not prioritized.
Ah sorry you can actually add 4 owners, but only if you do not check that you own more than 25% It does look like there is a way to add 5 if you get creative and first add 4 then check the box 😅 - but we are not doing anything about this in Web-Secure so I think maybe it's an edge case. |
Not really sure what is up with that text hmm... was it working before? First guess is we should not be nesting a |
Ah no it's actually a change in |
Alright, I think after this is merged we will be able to unblock hooking the |
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.
Looking good, minor question about size="micro"
for TextLink
<Text style={[styles.mt3, styles.textMicroSupporting]}> | ||
{this.props.translate('requestorStep.onFidoConditions')} | ||
<TextLink | ||
size="micro" |
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.
Why not just pass styles.textMicroSupporting
in the style
prop instead of introducing a new propType?
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.
If you move styles.link
to the end of the array of styles in TextLink.js
then you can just pass style={styles.textMicroSupporting}
here
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.
Couple reasons, but I did have a similar idea initially...
- the
additionalStyles
are added after everything else so the color intextMicroSupporting
would overwrite the link styles (which is undesirable since they lose the blue color and appearance as links)
- since this needed to be added a handful of things it seemed like a good idea to just bake it into the 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.
That said, we could undo this and add it with a style like textMicroSupportingLink
or remove the "color" from textMicroSupporting
and add it in with another style. But not really sure what is best here.
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.
If you move styles.link to the end of the array of styles in TextLink.js then you can just pass style={styles.textMicroSupporting} here
Right that just undoes what we did here, but I think the change @roryabraham made makes sense. Styles passed in as props should overwrite some base style and not come before the base styles.
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.
one sec, I think I've got a solution
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.
Looks good!
🚀 Deployed to staging in version: 1.0.71-2🚀
|
🚀 Deployed to production in version: 1.0.73-3🚀
|
cc @NikkiWines since this might affect validation stuff for the
RequestorStep
and builds on your work thereDetails
Hooking up the UI for the
ACHContractStep
. We will test the API flow in another PR.Fixed Issues
Fixes https://github.com/Expensify/Expensify/issues/166920
Tests
ACHContractStep
to show by modifying the logic hereQA Steps
No QA
Tested On
Screenshots
Web
Mobile Web
Desktop
iOS
Android