Added persistent Created Room Header to the Chat#7445
Conversation
|
@parasharrajat I do not have a mac or an iOS device atm, can you test it if it looks okay on those devices? Thanks :D |
|
Apart from it, I think there is more gap between first message and the Created view. @shawnborton Could you please review the design here? Thank you 🙇 . Leaving some images for broader view. When Chat is empty |
|
I think we might be able to widen that area a bit. In your screenshot, you can see how "him" falls to a third line because of how skinny that area is currently. |
From what I know, this is supposed to be added in the beginning of all Chat Reports (#7077 (comment))
EDIT: My bad, Width is set as 70% in ReportWelcomeText which is causing the wrapping of the text, will fix and push.
cc: @shawnborton , @parasharrajat |
|
Not a design expert. but I think it can be widened more. The Left and right side gap should be a minimum of 20px from screen edges. Thus there is enough space around so that |
|
I agree, I think we can just do 20px padding on the left and right with no max-width (just let it go full container) and we should be good to go. |
|
Updated Changes, the width specification matches that of the mockup now.Updated screenshots in the PR. |
parasharrajat
left a comment
There was a problem hiding this comment.
UI looks good. Just a small tweaks.
| pt5: { | ||
| paddingTop: 20, | ||
| }, | ||
|
|
There was a problem hiding this comment.
Please only add styles when they are used.
| pt5: { | |
| paddingTop: 20, | |
| }, |
| <View style={[styles.chatContent, | ||
| styles.pb8, | ||
| styles.p5, | ||
| ]} |
There was a problem hiding this comment.
| <View style={[styles.chatContent, | |
| styles.pb8, | |
| styles.p5, | |
| ]} | |
| <View style={[ | |
| styles.chatContent, | |
| styles.pb8, | |
| styles.p5, | |
| ]} |
| .filter(action => action.actionName === CONST.REPORT.ACTIONS.TYPE.IOU | ||
| || action.actionName === CONST.REPORT.ACTIONS.TYPE.ADDCOMMENT | ||
| || action.actionName === CONST.REPORT.ACTIONS.TYPE.RENAMED) | ||
| .filter(action => _.contains(_.values(CONST.REPORT.ACTIONS.TYPE), action.actionName)) |
There was a problem hiding this comment.
This doesn't seem like a safe change. We might have action types that should not be rendered in the future added to this list. Can we just add the new action to this list?
There was a problem hiding this comment.
.filter(action => action.actionName === CONST.REPORT.ACTIONS.TYPE.IOU
|| action.actionName === CONST.REPORT.ACTIONS.TYPE.ADDCOMMENT
|| action.actionName === CONST.REPORT.ACTIONS.TYPE.RENAMED
|| action.actionName === CONST.REPORT.ACTIONS.TYPE.CREATED)There was a problem hiding this comment.
Yes, that makes sense. Will do!
|
Updated with the requested changes! |
|
✋ 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 staging by @marcaaron in version: 1.1.36-0 🚀
|
|
🚀 Deployed to production by @roryabraham in version: 1.1.36-0 🚀
|





Details
We needed to replace the initial Room header with a persistent room header. I have added a new component that renders when action-type is
CREATED.I have also updated the names of a component and styles to reflect the change (Hope that's fine).
Fixed Issues
$ #7077
Tests
QA Steps
Tested On
Screenshots
Web
Screencast.from.27-01-22.08_07_07.PM.IST.mp4
Mobile Web
Desktop
iOS
Android