Skip to content

Refactored WorkspacePageWithSection#21917

Merged
arosiclair merged 12 commits into
Expensify:mainfrom
olexyt:16308_refactor_WorkspacePageWithSections
Jul 12, 2023
Merged

Refactored WorkspacePageWithSection#21917
arosiclair merged 12 commits into
Expensify:mainfrom
olexyt:16308_refactor_WorkspacePageWithSections

Conversation

@olexyt

@olexyt olexyt commented Jun 29, 2023

Copy link
Copy Markdown
Contributor

Details

Migrate WorkspacePageWithSection.js to function component

Fixed Issues

$ #16308
PROPOSAL: #16308 (comment)

Tests

  1. Click the Settings
  2. Click the Workspace
  3. Create a Workspace or choose a workspace
  4. Click all menus in RHN
    Should be showed all of panel
  • Verify that no errors appear in the JS console

Offline tests

Follow the same steps listed in the section above

QA Steps

Follow the same steps listed in the section above

  • Verify that no errors appear in the JS console

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 the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
    • 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 grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is 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 code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
  • 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
chrome.mp4
Mobile Web - Chrome
android-chrome.mp4
Mobile Web - Safari
iOS-safari.mov
Desktop
desktop.mov
iOS
iOS-app.mov
Android
android-app.mp4

@olexyt olexyt requested a review from a team as a code owner June 29, 2023 22:45
@melvin-bot melvin-bot Bot requested review from thesahindia and removed request for a team June 29, 2023 22:45
@melvin-bot

melvin-bot Bot commented Jun 29, 2023

Copy link
Copy Markdown

@thesahindia Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

@github-actions

github-actions Bot commented Jun 29, 2023

Copy link
Copy Markdown
Contributor

CLA Assistant Lite bot All contributors have signed the CLA ✍️ ✅

@olexyt

olexyt commented Jun 29, 2023

Copy link
Copy Markdown
Contributor Author

I have read the CLA Document and I hereby sign the CLA

Comment on lines +96 to +107
useEffect(() => {
fetchData();
}, [fetchData]);

fetchData() {
if (this.props.shouldSkipVBBACall) {
useEffect(() => {
if (network.isOffline) {
return;
}

BankAccounts.openWorkspaceView();
}

render() {
const achState = lodashGet(this.props.reimbursementAccount, 'achData.state', '');
const hasVBA = achState === BankAccount.STATE.OPEN;
const isUsingECard = lodashGet(this.props.user, 'isUsingExpensifyCard', false);
const policyID = lodashGet(this.props.route, 'params.policyID');
const policyName = lodashGet(this.props.policy, 'name');

return (
<ScreenWrapper
includeSafeAreaPaddingBottom={false}
shouldEnablePickerAvoiding={false}
fetchData();
}, [fetchData, network]);

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I think this can be improved. This is not making sense to me currently.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Hello @allroundexperts
Nice to meet you.
Thanks for your commenting.
Let me explain.
First useEffect function is for when component was mounted.
And second useEffect function is for when component was updated.
If we combine these 2 useEffect functions, fetchData function won't be called when component is mounted.
That means, fetchData function must be called at once without any relation with props changes.
So I defined first useEffect function.
Second useEffect function must be called whenever props is changed (but is called when network is online).
Thanks again.

@allroundexperts allroundexperts left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Rest of the changes look straight forward. Conditions inside componentDidUpdate need fine tuning.

@allroundexperts

Copy link
Copy Markdown
Contributor

@thesahindia I've done an initial review. If you want, you can take over from here. Else, please comment in the ticket and I'll handle the rest!

@olexyt

olexyt commented Jul 4, 2023

Copy link
Copy Markdown
Contributor Author

@allroundexperts @thesahindia
I've explained to your comment.
Please give me your thoughts.
Thanks.

@olexyt

olexyt commented Jul 7, 2023

Copy link
Copy Markdown
Contributor Author

Hello, @allroundexperts
I would be great if you can review and let me know what should I improve soon.
Can you please review my PR?

@allroundexperts

Copy link
Copy Markdown
Contributor

Hello, @allroundexperts

I would be great if you can review and let me know what should I improve soon.

Can you please review my PR?

Apologies. I was supposed to review it yesterday. Will do that today or over the weekend.

Comment on lines +96 to +106
useEffect(() => {
fetchData();
}, [fetchData]);

fetchData() {
if (this.props.shouldSkipVBBACall) {
useEffect(() => {
if (network.isOffline) {
return;
}

BankAccounts.openWorkspaceView();
}

render() {
const achState = lodashGet(this.props.reimbursementAccount, 'achData.state', '');
const hasVBA = achState === BankAccount.STATE.OPEN;
const isUsingECard = lodashGet(this.props.user, 'isUsingExpensifyCard', false);
const policyID = lodashGet(this.props.route, 'params.policyID');
const policyName = lodashGet(this.props.policy, 'name');

return (
<ScreenWrapper
includeSafeAreaPaddingBottom={false}
shouldEnablePickerAvoiding={false}
fetchData();
}, [fetchData, network]);

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I think this would more accurately mimic the behaviour in the previous class based component and will simplify the logic a lot as well:

useEffect(() => {
   if (shouldSkipVBBACall || isOffline) {
       return;
   }
   BankAccounts.openWorkspaceView();
}, [shouldSkipVBBACall, isOffline]);

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Hello, @allroundexperts
I used the useCallback for fetchData function for reducing reload and multiple define/execute fetchData function.
So I think we don't need shouldSkipVBBACall in useEffect.
Please let me know your thought.
Thanks.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I would suggest using the useOnNetworkReconnect hook for this case :

useOnNetworkReconnect(() => BankAccounts.openWorkspaceView());

@allroundexperts allroundexperts left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Looks good mostly. One small optimisation needed.

@allroundexperts

allroundexperts commented Jul 9, 2023

Copy link
Copy Markdown
Contributor

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 the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
    • 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 grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is 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 code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
  • 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-07-11.at.11.15.59.PM.mov
Mobile Web - Chrome
Screen.Recording.2023-07-11.at.11.23.02.PM.mov
Mobile Web - Safari
Screen.Recording.2023-07-11.at.11.21.15.PM.mov
Desktop
Screen.Recording.2023-07-11.at.11.18.54.PM.mov
iOS
Screen.Recording.2023-07-11.at.11.21.55.PM.mov
Android
Screen.Recording.2023-07-11.at.11.24.40.PM.mov

Comment on lines +96 to +106
useEffect(() => {
fetchData();
}, [fetchData]);

fetchData() {
if (this.props.shouldSkipVBBACall) {
useEffect(() => {
if (network.isOffline) {
return;
}

BankAccounts.openWorkspaceView();
}

render() {
const achState = lodashGet(this.props.reimbursementAccount, 'achData.state', '');
const hasVBA = achState === BankAccount.STATE.OPEN;
const isUsingECard = lodashGet(this.props.user, 'isUsingExpensifyCard', false);
const policyID = lodashGet(this.props.route, 'params.policyID');
const policyName = lodashGet(this.props.policy, 'name');

return (
<ScreenWrapper
includeSafeAreaPaddingBottom={false}
shouldEnablePickerAvoiding={false}
fetchData();
}, [fetchData, network]);

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I would suggest using the useOnNetworkReconnect hook for this case :

useOnNetworkReconnect(() => BankAccounts.openWorkspaceView());

WorkspacePageWithSections.displayName = 'WorkspacePageWithSections';

export default compose(
withLocalize,

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Seems like localize is not used in this component, let's remove it (remove props definition as well)

@olexyt olexyt Jul 10, 2023

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Hello, @fedirjh
For using useOnNetworkReconnect hook, if we use this hook, then we can't make fetchData function as useCallback because of React Hooks must be called in a React function component or a custom React Hook function.
So it is okay to remove useCallback from fetchData?
But lint recommends to use the useCallback.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Why do we use useCallback for fetchData ? it was not passed down to any child component so we should use regular function.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Because fetchData is using props.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

@olexyt fetchData is not necessary here. As stated above, we can just use a plain hook like:

useEffect(() => {
   if (shouldSkipVBBACall) {
       return;
   }
   BankAccounts.openWorkspaceView();
}, [shouldSkipVBBACall]);

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

@fedirjh
If we use the useOnNetworkReconnect, we can't handle shouldSkipVBBACall.

        // Line 90
        if (shouldSkipVBBACall) {
            return;
        }

What do you think?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

@olexyt Could be just updated to

useOnNetworkReconnect(() => !shouldSkipVBBACall && BankAccounts.openWorkspaceView());

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

@fedirjh
Can we remove network from propsType?
It is not used if we use the useOnNetworkReconnect.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

If it's not used, it should be removed.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

@fedirjh
Updated!
Please check again and let me know your thought.
Thanks.

function WorkspacePageWithSections(props) {
const {shouldSkipVBBACall} = props;

useOnNetworkReconnect(() => !shouldSkipVBBACall && BankAccounts.openWorkspaceView());

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

@olexyt We still need the componentDidMount equivalent hook that should run when component did mount, I would suggest the following :

Define fetchData outside of the component:

    fetchData(shouldSkipVBBACal) {
        if (shouldSkipVBBACall) {
            return;
        }

        BankAccounts.openWorkspaceView();
    }

Use useEffect hook that will run when component mount

    useEffect(() => {
        fetchData(shouldSkipVBBACall);
        // eslint-disable-next-line react-hooks/exhaustive-deps -- It should run when component mounts
    }, []);

Update the useOnNetworkReconnect hook to

useOnNetworkReconnect(() => fetchData(shouldSkipVBBACall));

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Updated following your suggestion.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Thank you for the quick update , it seems useOnNetworkReconnect was not updated yet.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Sorry @fedirjh
It was my mistake.
Now, I updated it.
Thanks.

@fedirjh fedirjh left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

There are still some unused code that should be removed, specifically withLocalize and withNetwork.

@olexyt

olexyt commented Jul 10, 2023

Copy link
Copy Markdown
Contributor Author

There are still some unused code that should be removed, specifically withLocalize and withNetwork.

@fedirjh
Updated!
I learnt many tricks and logic about Expensify due to your comments.
Thanks for your advices.

@fedirjh fedirjh left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Looks good to me , left a minor improvement.

<View style={[styles.w100, styles.flex1]}>{props.children(hasVBA, policyID, isUsingECard)}</View>
</ScrollViewWithContext>
) : (
props.children(hasVBA, policyID, isUsingECard)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

This code is used twice , could be dryed to

const content = children(hasVBA, policyID, isUsingECard);

footer and children could be destructed from props on top

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

@fedirjh
Updated!

@fedirjh fedirjh left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Looks good to me. @allroundexperts Looks good for the checklist.

@allroundexperts allroundexperts left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Looking good!

@melvin-bot

melvin-bot Bot commented Jul 11, 2023

Copy link
Copy Markdown

We did not find an internal engineer to review this PR, trying to assign a random engineer to #16308 as well as to this PR... Please reach out for help on Slack if no one gets assigned!

@melvin-bot melvin-bot Bot requested a review from arosiclair July 11, 2023 18:34
@olexyt

olexyt commented Jul 11, 2023

Copy link
Copy Markdown
Contributor Author

Hello @arosiclair @thesahindia
I will appreciate if you can check my PR asap.
Then I can take part to new round of migration.
Thanks.

includeSafeAreaPaddingBottom={false}
shouldEnablePickerAvoiding={false}
function WorkspacePageWithSections(props) {
const {children, footer, shouldSkipVBBACall} = props;

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Why deconstruct these props here and not above in the params?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Hello, @arosiclair
Nice to meet you.
It is possible to use the destructured props params?
I thought it prohibit to use destructured props params because all of function components are using props params directly.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

So what should I do for this? @arosiclair

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

You're allowed to destructure props now. We changed this not too long ago. So you can rewrite the above as

function WorkspacePageWithSections({children, footer, shouldSkipVBBACall}) {

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

@arosiclair
I just destructured props.
Please check again.
Thanks

Comment thread src/pages/workspace/WorkspacePageWithSections.js Outdated
Comment thread src/pages/workspace/WorkspacePageWithSections.js
@olexyt olexyt requested a review from arosiclair July 12, 2023 16:01

@arosiclair arosiclair left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

👍

@arosiclair arosiclair merged commit 573c3d3 into Expensify:main Jul 12, 2023
@OSBotify

Copy link
Copy Markdown
Contributor

✋ 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
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/arosiclair in version: 1.3.40-0 🚀

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

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/Julesssss in version: 1.3.40-5 🚀

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

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.

5 participants