-
Notifications
You must be signed in to change notification settings - Fork 3k
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
feat: Added Skeleton UI to chats #8042
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please mention platforms/devices on QA steps.
src/components/ChatGhostUI/ContentLoadingElements/ContentLoadingTwoLines/index.native.js
Outdated
Show resolved
Hide resolved
src/components/ChatGhostUI/ContentLoadingElements/ContentLoadingTwoLines/index.native.js
Outdated
Show resolved
Hide resolved
Please also look into this danilowoz/react-content-loader#125. Performance is crucial for this page. |
Fixing it. |
Conflicts again... 🙄 |
@parasharrajat Resolved the conflict and 1 comment that you raised. |
Conflicts again... |
Resolved @parasharrajat |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
code LGTM just noticed a small thing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems pagination is broken but that can't be caused by this PR. When pagination was working, this PR was working correctly. I am currently not sure how to test that correctly but to me, PR looks good.
cc: @Luke9389
PR 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 verified the steps for local testing are in the
- I checked that screenshots or videos are included for tests on all platforms
- I verified tests pass on all platforms & I tested again on:
- iOS / native
- Android / native
- iOS / Safari
- Android / Chrome
- MacOS / Chrome
- 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 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 notonIconClick
). - 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 was added in all
src/languages/*
files - I verified any copy / text that was added to the app is correct English and approved by marketing by tagging the marketing team 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 usingAvatar
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 */
- Any functional components have the
displayName
property - 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. foronClick={this.submit}
the methodthis.submit
should be bound tothis
in the constructor) - Any internal methods bound to
this
are necessary to be bound (i.e. avoidthis.submit = this.submit.bind(this);
ifthis.submit
is 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 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 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 thatAvatar
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.
- I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.
🎀 👀 🎀 C+ reviewed
Thanks @parasharrajat for the quick review on this one. @marcaaron Updated the comment, quick approval will move this forward. |
Merged! Before any more conflicts happen XD |
✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release. |
🚀 Deployed to production by @yuwenmemon in version: 1.1.87-9 🚀
|
Commenting for completion of the BZ checklist. This PR introduced a bug where the skeleton UI went over the edge of the screen on mobile. See PR for the fix. |
skeletonViewLines.push(<SkeletonViewLines numberOfRows={1} key={`skeletonViewLines${index}`} />); | ||
} | ||
} | ||
return <>{skeletonViewLines}</>; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should have been wrapped within a View. Otherwise the skeleton lines may shrink if the outer view height is not enough.
(Coming from a regression #19442)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Again, this was not needed at the time we built it so this can't be a regression from this PR. Later when the payment page was added it should have been adjusted to that case as well thus that PR should be linked as regression PR.
Our |
Details
react-content-loader
for SVG based animation on components.Fixed Issues
$ #7081
Tests
Tested the ghost screen on all platforms
Checked for responsive nature, ie, it should cover the full screen
Verified that it shows up only on the first load of the chat data
Verified that the expected order is maintained
Shouldn't show the screen if the report data already exists
Tested animation on switching between the chats
Verify that no errors appear in the JS console
PR Review Checklist
Contributor (PR Author) Checklist
main
### Fixed Issues
section abovesrc/languages/*
files (if applicable)Styling.md
) for all style edits I madeSTYLE.md
)Avatar
, I verified the components usingAvatar
are working as expected)main
branch)PR Reviewer Checklist
main
### Fixed Issues
section abovesrc/languages/*
files (if applicable)STYLE.md
) were followedAvatar
, I verified the components usingAvatar
are working as expected)main
branch)QA Steps
For all the platforms
Screenshots
Web
https://user-images.githubusercontent.com/3069065/175809839-cbb36e8e-0d77-4fb1-9060-f3ab57f43935.mov
https://user-images.githubusercontent.com/3069065/178344350-4115b23d-c006-49ae-86ae-e914ca6df577.mov
Mobile Web
https://user-images.githubusercontent.com/3069065/175809876-baaecb7b-bc49-4d4d-999f-56ca4e1f9783.mov
https://user-images.githubusercontent.com/3069065/175809892-59b58f60-c0c6-463b-be26-9fbecddcf288.mov
Desktop
https://user-images.githubusercontent.com/3069065/175809929-31a50372-d329-47dc-b173-03fa2aa95588.mov
https://user-images.githubusercontent.com/3069065/178345476-33e4a3ee-1858-48ad-b139-f65ccbe5b017.mp4
iOS
https://user-images.githubusercontent.com/3069065/175809976-ecf88fe7-046b-4c65-abb7-154d5efb89e7.mov
https://user-images.githubusercontent.com/3069065/175809984-14919ff4-ccdd-45e2-9188-0d7afee5488f.mov
Android
https://user-images.githubusercontent.com/3069065/175809992-09d82713-d87f-4fcd-a90e-1b9839947de7.mov
https://user-images.githubusercontent.com/3069065/175810023-584c8df6-f51a-41ca-97f1-f1cdee6645e0.mov