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

Navigate to #admin on workspace creation #22619

Merged
merged 5 commits into from
Jul 21, 2023

Conversation

esh-g
Copy link
Contributor

@esh-g esh-g commented Jul 11, 2023

Details

Fixed Issues

$ #21408
PROPOSAL: #21408 (comment)

Tests

Test 1

  1. Login from an account with no workspace (or delete all workspaces)
  2. Click on the + icon and create new workspace.
  3. On fullscreen, verify that we navigate to #admins page report and also to the workspace details on the right.
  4. On Small screen, verify that we are not shown the admin chat but are navigated to the details of the workspace.

Test 2

  1. Go to settings -> workspace.
  2. Click on "New Workspace"
  3. On fullscreen, verify that we navigate to #admins page report and also to the workspace details on the right.
  4. On Small screen, verify that we are not shown the admin chat but are navigated to the details of the workspace.

Test 3 (For web and mWeb)

  1. Login to Old dot.
  2. Go to settings -> policies -> groups.
  3. Click on new policy.
  4. Copy the URL and close the tab.
  5. Open a new tab and paste the URL replacing new.expensify.com with localhost:8080.
  6. On fullscreen, verify that we navigate to #admins page report and also to the workspace details on the right.
  7. On Small screen, verify that we are not shown the admin chat but are navigated to the details of the workspace.
  • Verify that no errors appear in the JS console

Offline tests

Test 2 (Only this test required for offline)

  1. Go to settings -> workspace.
  2. Click on "New Workspace"
  3. On fullscreen, verify that we navigate to #admins page report and also to the workspace details on the right.
  4. On Small screen, verify that we are not shown the admin chat but are navigated to the details of the workspace.

QA Steps

Test 1

  1. Login from an account with no workspace (or delete all workspaces)
  2. Click on the + icon and create new workspace.
  3. On fullscreen, verify that we navigate to #admins page report and also to the workspace details on the right.
  4. On Small screen, verify that we are not shown the admin chat but are navigated to the details of the workspace.

Test 2

  1. Go to settings -> workspace.
  2. Click on "New Workspace"
  3. On fullscreen, verify that we navigate to #admins page report and also to the workspace details on the right.
  4. On Small screen, verify that we are not shown the admin chat but are navigated to the details of the workspace.

Test 3 (For web and mWeb)

  1. Login to Old dot.
  2. Go to settings -> policies -> groups.
  3. Click on new policy.
  4. Copy the URL and close the tab.
  5. Open a new tab and paste the URL replacing new.expensify.com with staging.new.expensify.com
  6. On fullscreen, verify that we navigate to #admins page report and also to the workspace details on the right.
  7. On Small screen, verify that we are not shown the admin chat but are navigated to the details of the workspace.
  • 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
    • If we are not using the full Onyx data that we loaded, I've added the proper selector in order to ensure the component only re-renders when the data it is using changes
    • 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
Screen.Recording.2023-07-08.at.2.28.23.PM.mov
Screen.Recording.2023-07-14.at.8.29.14.PM.mov
Screen.Recording.2023-07-14.at.8.37.51.PM-1.mov
Mobile Web - Chrome
Screen.Recording.2023-07-11.at.11.56.22.AM.mov
Screen.Recording.2023-07-14.at.9.46.08.PM.mov
Screen.Recording.2023-07-14.at.9.43.44.PM-1.mov
Mobile Web - Safari
Screen.Recording.2023-07-11.at.11.29.58.AM.mov
Screen.Recording.2023-07-14.at.9.01.15.PM.mov
Screen.Recording.2023-07-14.at.9.05.15.PM.mov
Desktop
Screen.Recording.2023-07-11.at.11.45.10.AM.mov
Screen.Recording.2023-07-14.at.8.32.41.PM.mov
iOS
Screen.Recording.2023-07-08.at.2.42.29.PM.mov
Screen.Recording.2023-07-14.at.9.00.46.PM.mov
Android
Screen.Recording.2023-07-11.at.11.53.31.AM.mov
Screen.Recording.2023-07-14.at.9.25.36.PM.mov

@esh-g esh-g requested a review from a team as a code owner July 11, 2023 06:30
@melvin-bot melvin-bot bot requested review from abdulrahuman5196 and removed request for a team July 11, 2023 06:30
@melvin-bot
Copy link

melvin-bot bot commented Jul 11, 2023

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

@esh-g
Copy link
Contributor Author

esh-g commented Jul 12, 2023

bump @abdulrahuman5196 I hope this looks good! Hope we can get this done till tomorrow 😇

@abdulrahuman5196
Copy link
Contributor

Sorry for the delay. Will complete the review in the morning.

@abdulrahuman5196
Copy link
Contributor

@esh-g There is an another createWorkspace ingress here which is missed in the PR -

Policy.createWorkspace(policyOwnerEmail, makeMeAdmin, policyName, true);

@esh-g
Copy link
Contributor Author

esh-g commented Jul 13, 2023

@abdulrahuman5196 Then would it be fine to pass the shouldNavigateToAdminChat argument rom AuthScreen.js (App.setUpPoliciesAndNavigate) --> actions/App.js (Policy.createWorkspace). In there:

App.setUpPoliciesAndNavigate(this.props.session);

 App.setUpPoliciesAndNavigate(this.props.session, !this.props.isSmallScreenWidth);

@esh-g
Copy link
Contributor Author

esh-g commented Jul 13, 2023

@abdulrahuman5196 This is the only case where the function setUpPoliciesAndNavigate is being called as well, so it can be easily changed without affecting other places.

@abdulrahuman5196
Copy link
Contributor

abdulrahuman5196 commented Jul 13, 2023

Yes. Its should be fine. @esh-g

@esh-g
Copy link
Contributor Author

esh-g commented Jul 13, 2023

@abdulrahuman5196 I hope this looks good now!

@esh-g
Copy link
Contributor Author

esh-g commented Jul 13, 2023

@abdulrahuman5196 Do I need to merge main to this PR?

@abdulrahuman5196
Copy link
Contributor

@esh-g I don't see testing video for this #22619 (comment) and the settings->workspace creation flow?

And author's checklist testing steps also doesn't have the same?

@esh-g
Copy link
Contributor Author

esh-g commented Jul 14, 2023

@abdulrahuman5196 Sorry, I thought we only needed to add tests for the main bug.
I edited the Tests and am now creating the videos for the tests... But for Test 3, I'm not sure that is testable on native platforms...(because it involves manipulating URLs) Is it alright if I leave those out (for ios, android and desktop)?

@esh-g
Copy link
Contributor Author

esh-g commented Jul 14, 2023

@abdulrahuman5196 I have now added videos for all platforms as well (except the ones mentioned in the above comment)

@abdulrahuman5196
Copy link
Contributor

@esh-g For the old dot migration flow,

For some reason the LHN becomes unresponsive for me, but the same doesn't happen on main.

Screen.Recording.2023-07-14.at.11.55.17.PM.mov

@esh-g
Copy link
Contributor Author

esh-g commented Jul 15, 2023

@abdulrahuman5196 I merged main into this branch and it goes away.

Before

Screen.Recording.2023-07-15.at.11.28.09.AM-1.mov

After

Screen.Recording.2023-07-15.at.11.21.35.AM.mov

@esh-g
Copy link
Contributor Author

esh-g commented Jul 15, 2023

@abdulrahuman5196 Do let me know if that fixes it for you 😇

@esh-g
Copy link
Contributor Author

esh-g commented Jul 19, 2023

Bump @abdulrahuman5196

@esh-g
Copy link
Contributor Author

esh-g commented Jul 19, 2023

@abdulrahuman5196 Seems like another PR removed the logic to navigate to the admins chat as well as policy details from the Policy.createWorkspace and deferred the navigation to App.createWorkspaceAndNavigateToIt. Should I just replace the Navigation.setParams there like I did in this solution?

@abdulrahuman5196
Copy link
Contributor

abdulrahuman5196 commented Jul 19, 2023

Should I just replace the Navigation.setParams there like I did in this solution?

@esh-g Yes. Its only the position of the code that has changed. The same solution should apply AFAIK

@esh-g
Copy link
Contributor Author

esh-g commented Jul 19, 2023

@abdulrahuman5196 I have made the required changes!

@esh-g
Copy link
Contributor Author

esh-g commented Jul 20, 2023

bump @abdulrahuman5196

@abdulrahuman5196
Copy link
Contributor

Hi, will work on the review today

@abdulrahuman5196
Copy link
Contributor

Working on review now

@abdulrahuman5196
Copy link
Contributor

@esh-g Test 2 alone will be applicable for offline test as well

@abdulrahuman5196
Copy link
Contributor

abdulrahuman5196 commented Jul 21, 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 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-21.at.2.52.04.PM.mp4
Screen.Recording.2023-07-21.at.3.11.59.PM.mp4
Mobile Web - Chrome
az_recorder_20230721_151731.mp4
Mobile Web - Safari
Untitled.1.mp4
Desktop
Screen.Recording.2023-07-21.at.6.33.35.PM.mp4
iOS
Screen.Recording.2023-07-21.at.6.38.35.PM.mp4
Android
az_recorder_20230721_185519.mp4

@esh-g
Copy link
Contributor Author

esh-g commented Jul 21, 2023

@abdulrahuman5196 Made the change for offline tests 💫

Copy link
Contributor

@abdulrahuman5196 abdulrahuman5196 left a comment

Choose a reason for hiding this comment

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

Changes looks good and works well. Reviewers checklist is also complete.

All yours @aldo-expensify

🎀 👀 🎀
C+ Reviewed

@melvin-bot melvin-bot bot requested a review from aldo-expensify July 21, 2023 15:32
Copy link
Contributor

@aldo-expensify aldo-expensify left a comment

Choose a reason for hiding this comment

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

Tested well for me, thank you!

@aldo-expensify aldo-expensify merged commit f235a45 into Expensify:main Jul 21, 2023
@OSBotify
Copy link
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.

@@ -28,6 +28,7 @@ import * as ReimbursementAccountProps from '../ReimbursementAccount/reimbursemen
import * as ReportUtils from '../../libs/ReportUtils';
import * as CurrencyUtils from '../../libs/CurrencyUtils';
import withPolicyAndFullscreenLoading from './withPolicyAndFullscreenLoading';
import withWindowDimensions from '../../components/withWindowDimensions';
Copy link
Contributor

Choose a reason for hiding this comment

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

Minor feedback for next time, we have hooks to replace many of our HOCs, and we should strive to use them going forward in functional components

  • withWindowDimensions => useWindowDimensions
  • withLocalize => useLocalize
  • withNetwork => useNetwork

etc...

whenever refactoring a class component or adding new HOCs, please check src/hooks first. Thanks! 😄

@OSBotify
Copy link
Contributor

🚀 Deployed to staging by https://github.com/aldo-expensify in version: 1.3.45-0 🚀

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

@OSBotify
Copy link
Contributor

🚀 Deployed to production by https://github.com/mountiny in version: 1.3.45-7 🚀

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