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

[Internal QA] [Workspace Feeds] Pull the workspace feed data from different place in domain_member NVP #52268

Open
wants to merge 16 commits into
base: main
Choose a base branch
from

Conversation

VickyStash
Copy link
Contributor

@VickyStash VickyStash commented Nov 8, 2024

Explanation of Change

This PR implements getCompanyFeeds function which returns both custom and direct feeds.

Fixed Issues

$ #52251
PROPOSAL: N/A

Tests

  • Verify that no errors appear in the JS console
  1. Open the app.
  2. Go to the workspace with active custom feed and open Company cards page.
  3. Make sure the list of the cards is displayed as expected.
  4. Open any card details, make sure it looks as expected.
  5. Try to assign one more card, make sure the flow works correctly.
  6. In the console, past the next code:
Onyx.merge('sharedNVP_private_domain_member_YOUR_WORKSPACE_ACCOUNT_ID', {
    settings: {
        oAuthAccountDetails: {
            'oauth.chase.com': {
                accountList: ['CREDIT CARD...6607'],
                credentials: 'xxxxx',
                expiration: 1730998958,
            },
        },
    },
});
  1. Open the feed switcher and switch to the Chase feed.
  2. Repeat the step 6.
  3. Start the assign card flow from the Chase bank, make sure you see the cards to assign.
  4. Create a new workspace. Enable Company cards feature there and create a new custom feed. Make sure it's pending state looks as expected.

Offline tests

Same, as in the Tests section.

QA Steps

  • Verify that no errors appear in the JS console
  1. Open the app.
  2. Create a workspace and enable Company cards feature there.
  3. Add Custom feed.
  4. Assign a card inside the custom feed. Make sure it works as expected.
  5. The list of cards should look as expected. Open any of the cards to make sure it looks ok.
  6. Repeat steps 3-5 with a Direct feed.

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: mWeb Chrome
    • iOS: Native
    • iOS: mWeb 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 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 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 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.

Screenshots/Videos

Android: Native
android1.mp4
android2.mp4
Android: mWeb Chrome
android_web1.mp4
android_web2.mp4
iOS: Native
ios1.mp4
ios2.mp4
MacOS: Chrome / Safari
web_1.mp4
web2.mp4
web_3.mp4
MacOS: Desktop
desktop_1.mp4
desktop2.mp4

@VickyStash VickyStash changed the title [Workspace Feeds] Pull the workspace feed data from different place in domain_member NVP [WIP] [Workspace Feeds] Pull the workspace feed data from different place in domain_member NVP Nov 8, 2024
@VickyStash VickyStash changed the title [WIP] [Workspace Feeds] Pull the workspace feed data from different place in domain_member NVP [Workspace Feeds] Pull the workspace feed data from different place in domain_member NVP Nov 12, 2024
@VickyStash VickyStash marked this pull request as ready for review November 12, 2024 16:14
@VickyStash VickyStash requested a review from a team as a code owner November 12, 2024 16:14
@melvin-bot melvin-bot bot requested review from allgandalf and removed request for a team November 12, 2024 16:14
Copy link

melvin-bot bot commented Nov 12, 2024

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

@VickyStash
Copy link
Contributor Author

@allgandalf I haven't recorded ios web (Safari) video cause I have some troubles with it. I regularly see the error (on the main branch too). I guess it's something with my setup after long weekends, but could you please check it as well.

ios_web_error.mp4

Copy link
Contributor

@allgandalf allgandalf left a comment

Choose a reason for hiding this comment

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

Okay, great job! few minor comments, but i am confident we can merge this one today!

src/libs/CardUtils.ts Outdated Show resolved Hide resolved
src/libs/CardUtils.ts Outdated Show resolved Hide resolved
src/pages/workspace/WorkspaceInitialPage.tsx Outdated Show resolved Hide resolved
@@ -1,4 +1,8 @@
import * as cardUtils from '@src/libs/CardUtils';
Copy link
Contributor

Choose a reason for hiding this comment

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

@mountiny can you verify the unit tests, I see them just fine at first glance

@allgandalf
Copy link
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: 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 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
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari
MacOS: Desktop

@allgandalf
Copy link
Contributor

waiting for the workflows to pass ...

@allgandalf
Copy link
Contributor

@VickyStash please mark this one internal QA

@VickyStash
Copy link
Contributor Author

@allgandalf I think I don't have rights to update labels 🤔

@allgandalf
Copy link
Contributor

Oh i meant to update the title, @mountiny can add that label

@VickyStash VickyStash changed the title [Workspace Feeds] Pull the workspace feed data from different place in domain_member NVP [Internal QA] [Workspace Feeds] Pull the workspace feed data from different place in domain_member NVP Nov 13, 2024
@mountiny mountiny added the InternalQA This pull request required internal QA label Nov 13, 2024
@mountiny
Copy link
Contributor

Making a build

Copy link
Contributor

🧪🧪 Use the links below to test this adhoc build on Android, iOS, Desktop, and Web. Happy testing! 🧪🧪

Android 🤖 iOS 🍎
https://ad-hoc-expensify-cash.s3.amazonaws.com/android/52268/index.html https://ad-hoc-expensify-cash.s3.amazonaws.com/ios/52268/index.html
Android iOS
Desktop 💻 Web 🕸️
https://ad-hoc-expensify-cash.s3.amazonaws.com/desktop/52268/NewExpensify.dmg https://52268.pr-testing.expensify.com
Desktop Web

👀 View the workflow run that generated this build 👀

Copy link
Contributor

@mountiny mountiny left a comment

Choose a reason for hiding this comment

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

Couple small changes requested

src/libs/CardUtils.ts Outdated Show resolved Hide resolved
src/libs/CardUtils.ts Outdated Show resolved Hide resolved
src/types/onyx/CardFeeds.ts Outdated Show resolved Hide resolved
tests/unit/CardUtilsTest.ts Outdated Show resolved Hide resolved
src/libs/actions/CompanyCards.ts Show resolved Hide resolved
@allgandalf
Copy link
Contributor

I was able to assign cards from new policy , testing now....

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
InternalQA This pull request required internal QA Ready To Build
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants