Disable go to profile page for optimistic user#23802
Disable go to profile page for optimistic user#23802Julesssss merged 8 commits intoExpensify:mainfrom
Conversation
|
@sobitneupane 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] |
Julesssss
left a comment
There was a problem hiding this comment.
Just to confirm, after creating the request we should NOT be able to view the profile? In my case I could, but maybe this is due to my dev build not being truly offline?
Screen.Recording.2023-07-31.at.09.14.04.mov
sobitneupane
left a comment
There was a problem hiding this comment.
I was also able to reproduce the issue mentioned by @Julesssss.
Screen.Recording.2023-07-31.at.14.52.17.mov
|
@sobitneupane @Julesssss Yes, I've missed this avatar yet. Updated the PR to fix this issue. |
|
@sobitneupane Could you check again? Thanks |
sobitneupane
left a comment
There was a problem hiding this comment.
@dukenv0307 In split bill, I was unable to deselect newly added contact in offline.
Screen.Recording.2023-08-01.at.13.57.16.mov
|
The other thing I noticed was Disabled Mouse Cursor. @Julesssss Do we want to show disabled mouse cursor when user won't be able to go to Profile page? I think showing normal cursor instead of hand pointer should convey the message to user that the item is not pressable. |
|
@sobitneupane I think it's hard to display normal cursor because disable style of base components is disable cursor. |
@sobitneupane Updated to resolve this case. Please help to continue the review. |
Damn, in that case lets leave it for now. |
|
@sobitneupane Please help to review again when you have a chance. |
sobitneupane
left a comment
There was a problem hiding this comment.
Screenshots/Videos
Web
Screen.Recording.2023-08-02.at.14.59.45.mov
Screen.Recording.2023-08-02.at.15.09.01.mov
Mobile Web - Chrome
Mobile Web - Safari
Screen.Recording.2023-08-02.at.15.31.37.mov
Desktop
Screen.Recording.2023-08-02.at.15.20.49.mov
Screen.Recording.2023-08-02.at.15.24.09.mov
iOS
Screen.Recording.2023-08-02.at.15.34.16.mov
Android
Screen.Recording.2023-08-02.at.15.27.59.mov
Screen.Recording.2023-08-02.at.15.30.00.mov
|
@dukenv0307 There were few issues in the request money flow. Can you please merge main and check the following issues.
Screen.Recording.2023-08-02.at.15.34.16.mov |
|
@sobitneupane I just tested request money flow in main branch and has the same issue. This PR doesn't cause this issue. |
|
@sobitneupane #23962 Here is the deploy blocker of this issue above. I just run |
sobitneupane
left a comment
There was a problem hiding this comment.
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 Issuessection 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
Testssection - I verified the steps for Staging and/or Production testing are in the
QA stepssection - 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 verified the steps for local testing are in the
- 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.
toggleReportand notonIconClick). - 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 Copylabel 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
- 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.
- 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 usingAvatarhave 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
thisproperly so there are no scoping issues (i.e. foronClick={this.submit}the methodthis.submitshould be bound tothisin the constructor) - Any internal methods bound to
thisare necessary to be bound (i.e. avoidthis.submit = this.submit.bind(this);ifthis.submitis never passed to a component event handler likeonClick) - 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
Avataris modified, I verified thatAvataris 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
ScrollViewcomponent to make it scrollable when more elements are added to the page. - If the
mainbranch was merged into this PR after a review, I tested again and verified the outcome was still expected according to theTeststeps. - I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.
|
✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release. |
|
Hey guys, is this expected to prevent member of the room or anonymous from clicking header detail? hover.mov |
|
@hungvu193 Seems shouldDisablePage function is not working as expected. |
Yeah. There're 2 cases I think you need to improve that function, member of the room and anonymous user. |
|
@sobitneupane I think we have a regression here because I missed the case for chat room in |
|
@sobitneupane The draft is created, do we need to wait for issue created to open it or not? |
|
🚀 Deployed to staging by https://github.com/Julesssss in version: 1.3.50-0 🚀
|
I think you know this now, but yeah the PR should be created against the new bug issue. Then we can link it to this one via a comment. |
|
🚀 Deployed to production by https://github.com/puneetlath in version: 1.3.50-3 🚀
|
|
🚀 Deployed to staging by https://github.com/Julesssss in version: 1.3.51-0 🚀
|
|
🚀 Deployed to production by https://github.com/Julesssss in version: 1.3.51-2 🚀
|
| } else { | ||
| const formattedSelectedParticipants = _.map(props.selectedParticipants, (participant) => ({ | ||
| ...participant, | ||
| isDisabled: ReportUtils.isOptimisticPersonalDetail(participant.accountID), |
There was a problem hiding this comment.
Coming from #33976.
workspace's accountID is always 0, which resulting in it's always disabled. :)



Details
Disable go to profile page for optimistic user
Fixed Issues
$ #22691
PROPOSAL: #22691 (comment)
Tests
Offline tests
QA Steps
PR Author Checklist
### Fixed Issuessection aboveTestssectionOffline stepssectionQA stepssectiontoggleReportand notonIconClick)myBool && <MyComponent />.src/languages/*files and using the translation methodWaiting for Copylabel for a copy review on the original GH to get the correct copy.STYLE.md) were followedAvatar, I verified the components usingAvatarare working as expected)/** comment above it */thisproperly so there are no scoping issues (i.e. foronClick={this.submit}the methodthis.submitshould be bound tothisin the constructor)thisare necessary to be bound (i.e. avoidthis.submit = this.submit.bind(this);ifthis.submitis never passed to a component event handler likeonClick)StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG))Avataris modified, I verified thatAvataris working as expected in all cases)ScrollViewcomponent to make it scrollable when more elements are added to the page.mainbranch was merged into this PR after a review, I tested again and verified the outcome was still expected according to theTeststeps.Screenshots/Videos
Web
Screencast.from.29-07-2023.14.33.57.webm
Mobile Web - Chrome
Record_2023-07-29-14-38-51.1.mp4
Mobile Web - Safari
Screen.Recording.2023-07-29.at.15.54.59.mp4
Desktop
Screen.Recording.2023-07-29.at.15.46.05.2.mp4
iOS
Screen.Recording.2023-07-29.at.16.16.36.mp4
Android
22691.mp4