Skip to content
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

Refactor IOUModal to MoneyRequestModal #16679

Merged
merged 27 commits into from
Apr 5, 2023
Merged

Refactor IOUModal to MoneyRequestModal #16679

merged 27 commits into from
Apr 5, 2023

Conversation

thienlnam
Copy link
Contributor

@thienlnam thienlnam commented Mar 29, 2023

Details

Fixed Issues

$ https://github.com/Expensify/Expensify/issues/270592
$ #16276

Tests

This is a refactor of the IOUModal so lets test the main flows in all sorts of ways

  • Request Money
  1. Request money via the global create
  2. Update the currency to something random
  3. Select a participant
  4. Verify a transaction is created between you and the participant
  • Split bill
  1. Split bill via the global create
  2. Update the currency to USD
  3. Select 8 participants and notice you see the text You've selected the maximum number (8) of participants.
  4. Continue and write a description
  5. Notice that a group chat was created, and in each DM a message was sent
  • Send Money
  1. Send money via the global create
  2. Update the currency to USD
  3. Select a participant and hit 'Settle outside of Expensify'
  4. Verify it works as expected
  • Verify that the nothing about the IOU functionality has changed

  • Verify that no errors appear in the JS console

Offline tests

  1. Go through all of the flows offline and then go back online and verify they work as expected

QA Steps

Same steps as Tests

PR Author Checklist

  • I linked the correct issue in the ### Fixed Issues section above
  • I wrote clear testing steps that cover the changes made in this PR
    • I added steps for local testing in the Tests section
    • I added steps for the expected offline behavior in the Offline steps section
    • I added steps for Staging and/or Production testing in the QA steps section
    • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
    • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
  • I included screenshots or videos for tests on all platforms
  • I ran the tests on all platforms & verified they passed on:
    • Android / native
    • Android / Chrome
    • iOS / native
    • iOS / Safari
    • MacOS / Chrome / Safari
    • MacOS / Desktop
  • I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
  • I followed proper code patterns (see Reviewing the code)
    • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
    • I verified that comments were added to code that is not self explanatory
    • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
    • I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
      • If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
    • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
    • I verified any copy / text that was added to the app is correct English and approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
    • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
    • I verified the JSDocs style guidelines (in STYLE.md) were followed
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I followed the guidelines as stated in the Review Guidelines
  • I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
  • I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
  • I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
  • I verified that if a function's arguments changed that all usages have also been updated correctly
  • If a new component is created I verified that:
    • A similar component doesn't exist in the codebase
    • All props are defined accurately and each prop has a /** comment above it */
    • The file is named correctly
    • The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
    • The only data being stored in the state is data necessary for rendering and nothing else
    • For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
    • Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
    • All JSX used for rendering exists in the render method
    • The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
  • If any new file was added I verified that:
    • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
  • If a new CSS style is added I verified that:
    • A similar style doesn't already exist
    • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)
  • If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
  • If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
  • If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
  • If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
  • I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Screenshots/Videos

Web
Screen.Recording.2023-04-03.at.4.48.28.PM.mov
Mobile Web - Chrome
Screen.Recording.2023-04-04.at.11.29.55.AM.mov
Mobile Web - Safari
Screen.Recording.2023-04-04.at.11.36.47.AM.mov
Desktop
Screen.Recording.2023-04-03.at.6.05.03.PM.mov
iOS
Android

Copy link
Contributor

@marcaaron marcaaron left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looking pretty 👌. Left a few notes on the hooks stuff.

const isDoneCreatingIOUTransaction = prevCreatingIOUTransactionStatusRef.current && !lodashGet(props, 'iou.creatingIOUTransaction');

// User came back online, so we can try to create the IOU transaction again
if (prevNetworkStatusRef.current && !props.network.isOffline) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

NAB / maybe for a follow up. But I would consider refactoring this logic into a custom hook called useNetworkReconnect() that does something like this:

exports the context object from here:

const [withNetwork, NetworkProvider] = createOnyxContext(ONYXKEYS.NETWORK);
const [withPersonalDetails, PersonalDetailsProvider] = createOnyxContext(ONYXKEYS.PERSONAL_DETAILS);

function useNetworkReconnect(callback) {
    const {isOffline} = useContext(NetworkContext);
    const prevIsOfflineRef = useRef(isOffline);
    useEffect(() => {
        if (prevIsOfflineRef.current && !isOffline) {
            callback();
        }

        prevIsOfflineRef.current = isOffline;
    }, [isOffline]);
}

and would be used like this

useNetworkReconnect(PersonalDetails.openMoneyRequestModalPage);

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree it would be nice to have a seperate hook for this, I'll create another issue that will go in and just refactor all instances of it

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

const selectedCurrencyCode = lodashGet(props, 'iou.selectedCurrencyCode');
if (prevSelectedCurrencyCodeRef.current !== selectedCurrencyCode) {
IOU.setIOUSelectedCurrency(selectedCurrencyCode);
}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

NAB, but feel like I don't understand it or maybe it's an anti-pattern. Why is the currency changing? Can we just update this whenever the currency changes (e.g. by moving IOU.setIOUSelectedCurrency() closer to the logic that updates the prop instead of applying a side effect)?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah I also agree this is an anti-pattern, I would imagine we call this where the logic happens of the user changing their currency code

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

... I went to the spot where the currency is selected and it already does this so I am going to 🔪 it from here and see what breaks

</View>
</View>
);
}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pretty much all of these functions should use useCallback() if they have dependencies.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

And if they don't we can move them to the top of the file. I looked briefly and I think most do have dependencies.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What's the guideline for when to cache methods? I didn't think it was necessary here because none of these functions perform any heavy computational tasks that need to be cached

@thienlnam
Copy link
Contributor Author

This is ready to be reviewed, I still need to add screenshots but we can do a code review
cc @marcaaron @Julesssss @luacmartins @mountiny

@thienlnam thienlnam requested review from fedirjh and removed request for rushatgabhane April 4, 2023 18:42
Copy link
Contributor

@marcaaron marcaaron left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Each time we render this component the inline functions with dependencies inside it will get re-created. Based on this conversation we have decided to just wrap those with useCallback().

Full context here: https://expensify.slack.com/archives/C01GTK53T8Q/p1680096510744619

* A modal used for requesting money, splitting bills or sending money.
*/
const propTypes = {
/** Whether the IOU is for a single request or a group bill split */
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nab, should we change some of these IOU to Request?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated some of them to Request - didn't update all of them because they are still IOU reports and used like that throughout the code so didn't want it to cause more confusion

useEffect(() => {
PersonalDetails.openMoneyRequestModalPage();
IOU.setIOUSelectedCurrency(props.currentUserPersonalDetails.localCurrencyCode);
// eslint-disable-next-line react-hooks/exhaustive-deps -- props.currentUserPersonalDetails will always exist from Onyx
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it's not needed because we get it from onyx

And because we do not want this effect to run again.

I think it's kind of an anti-pattern though (that we can clean up later probably). If we always want the "iou selected currency" to be the "local currency code" when this component mounts then we should update that value in Onyx whenever we update the local currency code. We can hook into the initial render like this - but it's not obvious if we should...


useEffect(() => {
// We only want to check if we just finished creating an IOU transaction
// We check it within this effect because we're sending the request optimistically but if an error occurs from the API, we will update the iou state with the error later
Copy link
Contributor

@marcaaron marcaaron Apr 4, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it kind of sus and/or confusing? If the error occurs from the API then could we just look at props.iou.error as a dependency? If we didn't have an error before, but have one now then we should set the index to 0.

also having trouble understanding the case where we'd dismiss the modal. Anytime the iou changes and we have no errors and we're not in the process of creating the transaction via the API we call dismissModal()? Why is that exactly?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah I agree it is kind of confusing

If the error occurs from the API then could we just look at props.iou.error as a dependency?

We could, but we'd still need to check the previous props to see if we are done creating iou otherwise this would run each re-render

also having trouble understanding the case where we'd dismiss the modal. Anytime the iou changes and we have no errors and we're not in the process of creating the transaction via the API we call dismissModal()? Why is that exactly?

Don't have a great answer for this, I'm mostly just refactoring the existing logic in place

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My guess actually is that we have this logic in place for the offline handling of creating IOUs. Like if you dismiss the modal right after the transaction was created, then we don't have the ability to re-open and restart the money request. This handling is basically like - user comes back online? okay open the money request modal and then now that they are back online based on the success state of the IOU either restart the modal or dismiss it

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok, I think at a minimum we should just add a more specific dependency for creatingIOUTransaction? If I am understanding the logic correctly we only want to do "something" (show error or dismiss) when the transaction API call completes.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe we're already kind of handling this with prevCreatingIOUTransactionStatusRef, like we need to check that creatingIOUTransaction is true but also that the previous creatingIOUTransaction is false to confirm this is the first time that the IOU was created

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

More weirdness happening, creating this issue #16942 to investigate it more deeply but not block on this

@thienlnam
Copy link
Contributor Author

Okay, there's some more weird logic to clean up but I don't want to keep holding this PR for these changes bc many other PRs are on hold for this.

I created another issue to investigate more deeply here #16942 but this will at least unblock the other PRs. Right now, this uses mostly the same logic that was already existing

@thienlnam
Copy link
Contributor Author

Ready to review / test!

@thienlnam thienlnam requested review from marcaaron and fedirjh April 4, 2023 23:03
@fedirjh
Copy link
Contributor

fedirjh commented Apr 4, 2023

Reviewer Checklist

  • I have verified the author checklist is complete (all boxes are checked off).
  • I verified the correct issue is linked in the ### Fixed Issues section above
  • I verified testing steps are clear and they cover the changes made in this PR
    • I verified the steps for local testing are in the Tests section
    • I verified the steps for Staging and/or Production testing are in the QA steps section
    • I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
  • I checked that screenshots or videos are included for tests on all platforms
  • I included screenshots or videos for tests on all platforms
  • I verified tests pass on all platforms & I tested again on:
    • Android / native
    • Android / Chrome
    • iOS / native
    • iOS / Safari
    • MacOS / Chrome / Safari
    • MacOS / Desktop
  • If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
  • I verified proper code patterns were followed (see Reviewing the code)
    • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
    • I verified that comments were added to code that is not self explanatory
    • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
    • I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
    • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
    • I verified any copy / text that was added to the app is correct English and approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
    • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
    • I verified the JSDocs style guidelines (in STYLE.md) were followed
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I verified that this PR follows the guidelines as stated in the Review Guidelines
  • I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
  • I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
  • I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
  • If a new component is created I verified that:
    • A similar component doesn't exist in the codebase
    • All props are defined accurately and each prop has a /** comment above it */
    • The file is named correctly
    • The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
    • The only data being stored in the state is data necessary for rendering and nothing else
    • For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
    • Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
    • All JSX used for rendering exists in the render method
    • The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
  • If any new file was added I verified that:
    • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
  • If a new CSS style is added I verified that:
    • A similar style doesn't already exist
    • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)
  • If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
  • If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
  • If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
  • If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
  • I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Web
Screen.Recording.2023-04-04.at.9.20.42.PM.mov

Offline test

Screen.Recording.2023-04-05.at.12.51.06.AM.mov
Mobile Web - Chrome
Screen.Recording.2023-04-04.at.10.45.25.PM.mov
Mobile Web - Safari
Simulator.Screen.Recording.-.iPhone.14.-.2023-04-04.at.22.24.30.mp4
Desktop
Screen.Recording.2023-04-04.at.9.35.28.PM.mov
iOS
Simulator.Screen.Recording.-.iPhone.14.-.2023-04-04.at.22.18.06.mp4
Android
Screen.Recording.2023-04-04.at.10.51.47.PM.mov

Copy link
Contributor

@marcaaron marcaaron left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM - full disclosure I did not test the changes yet, but will give it a go if needed.

Comment on lines +109 to +133
const participantsWithDetails = _.map(OptionsListUtils.getPersonalDetailsForLogins(reportParticipants, props.personalDetails), personalDetails => ({
login: personalDetails.login,
text: personalDetails.displayName,
firstName: lodashGet(personalDetails, 'firstName', ''),
lastName: lodashGet(personalDetails, 'lastName', ''),
alternateText: Str.isSMSLogin(personalDetails.login) ? Str.removeSMSDomain(personalDetails.login) : personalDetails.login,
icons: [{
source: ReportUtils.getAvatar(personalDetails.avatar, personalDetails.login),
name: personalDetails.login,
type: CONST.ICON_TYPE_AVATAR,
}],
keyForList: personalDetails.login,
payPalMeAddress: lodashGet(personalDetails, 'payPalMeAddress', ''),
phoneNumber: lodashGet(personalDetails, 'phoneNumber', ''),
}));

// Skip IOUParticipants step if participants are passed in
const steps = reportParticipants.length ? [Steps.IOUAmount, Steps.IOUConfirm] : [Steps.IOUAmount, Steps.IOUParticipants, Steps.IOUConfirm];

const prevCreatingIOUTransactionStatusRef = useRef(lodashGet(props.iou, 'creatingIOUTransaction'));
const prevNetworkStatusRef = useRef(props.network.isOffline);

const [previousStepIndex, setPreviousStepIndex] = useState(0);
const [currentStepIndex, setCurrentStepIndex] = useState(0);
const [participants, setParticipants] = useState(participantsWithDetails);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Another possible follow up, but we should definitely use a lazy init for useState() here.. we need to pull the logic from line 109 down into the useState() call so we only calculate it once instead of on every render (might not be hurting anything but it's unnecessary work)...

Suggested change
const participantsWithDetails = _.map(OptionsListUtils.getPersonalDetailsForLogins(reportParticipants, props.personalDetails), personalDetails => ({
login: personalDetails.login,
text: personalDetails.displayName,
firstName: lodashGet(personalDetails, 'firstName', ''),
lastName: lodashGet(personalDetails, 'lastName', ''),
alternateText: Str.isSMSLogin(personalDetails.login) ? Str.removeSMSDomain(personalDetails.login) : personalDetails.login,
icons: [{
source: ReportUtils.getAvatar(personalDetails.avatar, personalDetails.login),
name: personalDetails.login,
type: CONST.ICON_TYPE_AVATAR,
}],
keyForList: personalDetails.login,
payPalMeAddress: lodashGet(personalDetails, 'payPalMeAddress', ''),
phoneNumber: lodashGet(personalDetails, 'phoneNumber', ''),
}));
// Skip IOUParticipants step if participants are passed in
const steps = reportParticipants.length ? [Steps.IOUAmount, Steps.IOUConfirm] : [Steps.IOUAmount, Steps.IOUParticipants, Steps.IOUConfirm];
const prevCreatingIOUTransactionStatusRef = useRef(lodashGet(props.iou, 'creatingIOUTransaction'));
const prevNetworkStatusRef = useRef(props.network.isOffline);
const [previousStepIndex, setPreviousStepIndex] = useState(0);
const [currentStepIndex, setCurrentStepIndex] = useState(0);
const [participants, setParticipants] = useState(participantsWithDetails);
// Skip IOUParticipants step if participants are passed in
const steps = reportParticipants.length ? [Steps.IOUAmount, Steps.IOUConfirm] : [Steps.IOUAmount, Steps.IOUParticipants, Steps.IOUConfirm];
const prevCreatingIOUTransactionStatusRef = useRef(lodashGet(props.iou, 'creatingIOUTransaction'));
const prevNetworkStatusRef = useRef(props.network.isOffline);
const [previousStepIndex, setPreviousStepIndex] = useState(0);
const [currentStepIndex, setCurrentStepIndex] = useState(0);
const [participants, setParticipants] = useState(() => _.map(OptionsListUtils.getPersonalDetailsForLogins(reportParticipants, props.personalDetails), personalDetails => ({
login: personalDetails.login,
text: personalDetails.displayName,
firstName: lodashGet(personalDetails, 'firstName', ''),
lastName: lodashGet(personalDetails, 'lastName', ''),
alternateText: Str.isSMSLogin(personalDetails.login) ? Str.removeSMSDomain(personalDetails.login) : personalDetails.login,
icons: [{
source: ReportUtils.getAvatar(personalDetails.avatar, personalDetails.login),
name: personalDetails.login,
type: CONST.ICON_TYPE_AVATAR,
}],
keyForList: personalDetails.login,
payPalMeAddress: lodashGet(personalDetails, 'payPalMeAddress', ''),
phoneNumber: lodashGet(personalDetails, 'phoneNumber', ''),
})));

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good point, will add that to the list of things to do in #16942

@MelvinBot
Copy link

🎯 @fedirjh, thanks for reviewing and testing this PR! 🎉

An E/App issue has been created to issue payment here: #16944.

@marcaaron
Copy link
Contributor

Gonna merge this so we can keep the Manual Requests train rolling 🚅

@marcaaron marcaaron merged commit ce1dccb into main Apr 5, 2023
@marcaaron marcaaron deleted the jack-refactorIOUModal branch April 5, 2023 00:29
@OSBotify
Copy link
Contributor

OSBotify commented Apr 5, 2023

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

@OSBotify
Copy link
Contributor

OSBotify commented Apr 5, 2023

🚀 Deployed to staging by https://github.com/marcaaron in version: 1.2.95-0 🚀

platform result
🤖 android 🤖 success ✅
🖥 desktop 🖥 success ✅
🍎 iOS 🍎 success ✅
🕸 web 🕸 success ✅

@OSBotify
Copy link
Contributor

OSBotify commented Apr 6, 2023

🚀 Deployed to production by https://github.com/thienlnam in version: 1.2.95-0 🚀

platform result
🤖 android 🤖 success ✅
🖥 desktop 🖥 success ✅
🍎 iOS 🍎 success ✅
🕸 web 🕸 success ✅

};

const ModalHeader = props => (
<View style={[styles.headerBar]}>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There was some inconsistency in styling Header with Back button. It was fixed by this PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants