feat: create usePolicy hook #46956

daledah · 2024-08-07T10:58:47Z

Details

Fixed Issues

$ #46805
PROPOSAL: #46805 (comment)

Tests

As User A Create a group chat with User B While viewing both accounts
go to user B > navigate to the group chat created
Click on the + button on the composer box > Split Expense
Enter amount > Click next. Don't finish the flow
As User A,While User B is the confirmation page, remove user B from the group.
Verify that: Error is shown instead of App crash

Verify that no errors appear in the JS console

Offline tests

QA Steps

As User A Create a group chat with User B While viewing both accounts
go to user B > navigate to the group chat created
Click on the + button on the composer box > Split Expense
Enter amount > Click next. Don't finish the flow
As User A,While User B is the confirmation page, remove user B from the group.
Verify that: Error is shown instead of App crash

Verify that no errors appear in the JS console

PR Author Checklist

Screenshots/Videos

Android: Native

Screen.Recording.2024-08-07.at.22.20.39.mp4

Android: mWeb Chrome

Screen.Recording.2024-08-07.at.22.06.21.mp4

iOS: Native

Screen.Recording.2024-08-07.at.23.21.37.mp4

iOS: mWeb Safari

Screen.Recording.2024-08-07.at.22.10.39.mp4

MacOS: Chrome / Safari

Screen.Recording.2024-08-07.at.17.52.35.mp4

MacOS: Desktop

Screen.Recording.2024-08-07.at.22.14.46.mp4

melvin-bot · 2024-08-07T16:24:48Z

@ishpaul777 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]

src/hooks/usePolicy.ts

daledah · 2024-08-07T17:46:41Z

@roryabraham thanks for the recommendation. I updated the PR.

ishpaul777 · 2024-08-08T16:00:14Z

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: mWeb Chrome
- iOS: Native
- iOS: mWeb 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 either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
- 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(theme.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 the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
- I verified that all the inputs inside a form are aligned with each other.
- I added Design label and/or tagged @Expensify/design so the design team can review the changes.
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

Android: Native

WhatsApp.Video.2024-08-08.at.11.16.20.PM.mp4

Android: mWeb Chrome

WhatsApp.Video.2024-08-08.at.11.13.08.PM.mp4

iOS: Native

Screen.Recording.2024-08-08.at.10.52.46.PM.mov

iOS: mWeb Safari

Screen.Recording.2024-08-08.at.10.58.20.PM.mov

MacOS: Chrome / Safari

Screen.Recording.2024-08-08.at.10.54.36.PM.mov

MacOS: Desktop

Screen.Recording.2024-08-08.at.11.25.29.PM.mov

ishpaul777 · 2024-08-08T18:00:17Z

src/pages/home/report/ReportActionItemContentCreated.tsx

@@ -52,7 +53,7 @@ function ReportActionItemContentCreated({contextValue, parentReportAction, trans

    const {report, action, transactionThreadReport} = contextValue;

-    const [policy] = useOnyx(`${ONYXKEYS.COLLECTION.POLICY}${report.policyID === CONST.POLICY.OWNER_EMAIL_FAKE ? '-1' : report.policyID ?? '-1'}`);
+    const policy = usePolicy(report.policyID === CONST.POLICY.OWNER_EMAIL_FAKE ? '-1' : report.policyID ?? '-1');


NAB, passing report.policyID should be enough here

OSBotify · 2024-08-08T22:24:58Z

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

Beamanator · 2024-08-14T20:54:19Z

FYI I believe this was deployed to prod yesterday, from this checklist - #47219

daledah added 2 commits August 7, 2024 17:42

feat: create usePolicy hook

e5786c9

fix: typecheck

7498f6a

daledah marked this pull request as ready for review August 7, 2024 16:24

daledah requested a review from a team as a code owner August 7, 2024 16:24

melvin-bot bot requested a review from ishpaul777 August 7, 2024 16:24

melvin-bot bot removed the request for review from a team August 7, 2024 16:24

daledah mentioned this pull request Aug 7, 2024

[$250] Group - App crash when removing a member on the process splitting expense #46805

Closed

6 tasks

roryabraham requested changes Aug 7, 2024

View reviewed changes

src/hooks/usePolicy.ts Outdated Show resolved Hide resolved

daledah added 3 commits August 8, 2024 00:22

fix: move getPolicyId to outside of usePolicy

5b0d5a3

fix: move getPolicyId to outside of usePolicy

b15eb1d

fix: typo

763ecd1

roryabraham approved these changes Aug 8, 2024

View reviewed changes

ishpaul777 reviewed Aug 8, 2024

View reviewed changes

roryabraham merged commit e14fc68 into Expensify:main Aug 8, 2024
15 of 16 checks passed

roryabraham mentioned this pull request Aug 9, 2024

Scan - App crashes when submitting a scan expense via QAB #47175

Closed

6 tasks

github-actions bot mentioned this pull request Aug 12, 2024

Deploy Checklist: New Expensify 2024-08-12 #47219

Closed

90 tasks

ishpaul777 mentioned this pull request Aug 14, 2024

[$250] [CRITICAL] [CVP] Track Expense - App crashes when tracking an expense #46879

Closed

6 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

feat: create usePolicy hook #46956

feat: create usePolicy hook #46956

daledah commented Aug 7, 2024 •

edited

Loading

melvin-bot bot commented Aug 7, 2024

daledah commented Aug 7, 2024

ishpaul777 commented Aug 8, 2024 •

edited

Loading

ishpaul777 Aug 8, 2024 •

edited

Loading

OSBotify commented Aug 8, 2024

Beamanator commented Aug 14, 2024

feat: create usePolicy hook #46956

feat: create usePolicy hook #46956

Conversation

daledah commented Aug 7, 2024 • edited Loading

Details

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

melvin-bot bot commented Aug 7, 2024

daledah commented Aug 7, 2024

ishpaul777 commented Aug 8, 2024 • edited Loading

Reviewer Checklist

Screenshots/Videos

ishpaul777 Aug 8, 2024 • edited Loading

Choose a reason for hiding this comment

OSBotify commented Aug 8, 2024

Beamanator commented Aug 14, 2024

daledah commented Aug 7, 2024 •

edited

Loading

ishpaul777 commented Aug 8, 2024 •

edited

Loading

ishpaul777 Aug 8, 2024 •

edited

Loading