-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
Migrate welcome message to room description for report #34150
Conversation
@rushatgabhane 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] |
Some things that are pending:
@rushatgabhane Could you please also confirm the test steps? I'll attach the videos once I know they are correct! |
This is in progress. I'll let you know when it's live.
This is in-progress. We'll save it as JSON `{'html': 'this is the description'}' like we do for the welcome message today.
Can you post these in the #expensify-open-source channel and I'll make sure they get confirmed.
Can you expand on this? What is the problem? |
@puneetlath I have posted the translations here
@puneetlath Currently, the path |
gentle bump @rushatgabhane on the review... |
@esh-g thank you for the changes. The app doesn't crash now |
Bug: when creating a new room with a descpription, the description doesn't persist.
Screen.Recording.2024-01-15.at.11.08.50.mov |
@rushatgabhane This is because backend doesn't save the description for now. I already highlighted this here: #32615 (comment) |
This is live now on staging.
This is live now on staging.
Asked in the internal channel. Should hear back on this soon.
I think we could use /description for both. Unless it creates some sort of problem. Ultimately, they are both for setting the "description" field on a report. |
@puneetlath @rushatgabhane I have another question: |
To do that, I'm thinking of making the
|
Yes, any workspace member who is also a member of the room should be able to change the description.
Makes sense to me. cc @rushatgabhane in case you have any concerns. |
To achieve same route paths Also, from product perspective, the task description is same as a room description. i.e. a short summary of what the task is / what the room is for. I'm okay with this. |
It seems like it wasn't part of the scope, though I think it should be. We can handle that as a follow-up. |
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.
Some very minor comments, great job with this!
Co-authored-by: Puneet Lath <puneet@expensify.com>
Co-authored-by: Puneet Lath <puneet@expensify.com>
Co-authored-by: Puneet Lath <puneet@expensify.com>
✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release. |
🚀 Cherry-picked to staging by https://github.com/thienlnam in version: 1.4.36-5 🚀
@Expensify/applauseleads please QA this PR and check it off on the deploy checklist if it passes. |
1 similar comment
🚀 Cherry-picked to staging by https://github.com/thienlnam in version: 1.4.36-5 🚀
@Expensify/applauseleads please QA this PR and check it off on the deploy checklist if it passes. |
This PR is failing because of issue #35901 The issue is reproducible in: Web, mWeb/Chrome, Android, IOS Bug6369339_1707227714073.Recording__2100.mp4 |
Yes, this is because the backend markdown handling is pending |
Yep, that's a known issue that is being worked on. |
🚀 Deployed to production by https://github.com/Julesssss in version: 1.4.37-7 🚀
|
@ishpaul777 @esh-g We set |
I think this was intentional to resolve #34150 (comment) |
<FullPageNotFoundView shouldShow={!ReportUtils.canEditReportDescription(report, policy)}> | ||
<HeaderWithBackButton | ||
title={translate('reportDescriptionPage.roomDescription')} | ||
onBackButtonPress={() => Navigation.goBack(ROUTES.REPORT_WITH_ID_DETAILS.getRoute(report.reportID))} |
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 approach isn't perfect after we enable deep linking to room description page from room header.
Now no longer need param in goBack.
|
||
const optimisticData: OnyxUpdate[] = [ | ||
{ | ||
onyxMethod: Onyx.METHOD.MERGE, | ||
key: `${ONYXKEYS.COLLECTION.REPORT}${reportID}`, | ||
value: {welcomeMessage: parsedWelcomeMessage}, | ||
value: {description: parsedDescription, pendingFields: {description: CONST.RED_BRICK_ROAD_PENDING_ACTION.UPDATE}}, |
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.
We should had created a optimistic action here, this caused #46046
Details
Fixed Issues
$ #32615
PROPOSAL: #32615 (comment)
Tests
[The markdown is still not supported on backend (as of 31/Jan)]
Offline tests
QA Steps
[The markdown is still not supported on backend (as of 31/Jan)]
PR Author Checklist
### Fixed Issues
section aboveTests
sectionOffline steps
sectionQA steps
sectiontoggleReport
and notonIconClick
)myBool && <MyComponent />
.src/languages/*
files and using the translation methodWaiting for Copy
label for a copy review on the original GH to get the correct copy.STYLE.md
) were followedAvatar
, I verified the components usingAvatar
are working as expected)StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)
)Avatar
is modified, I verified thatAvatar
is working as expected in all cases)Design
label so the design team can review the changes.ScrollView
component to make it scrollable when more elements are added to the page.main
branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to theTest
steps.Screenshots/Videos
Android: Native
Screen.Recording.2024-02-01.at.3.38.10.PM.mov
Android: mWeb Chrome
Screen.Recording.2024-01-31.at.7.09.07.PM.mov
iOS: Native
fcaab924-1f36-4c33-961a-7dfe1347c158.mp4
iOS: mWeb Safari
Screen.Recording.2024-01-30.at.10.09.56.PM.mov
MacOS: Chrome / Safari
Screen.Recording.2024-01-30.at.10.01.40.PM.mov
Screen.Recording.2024-01-31.at.9.11.46.PM.mov
MacOS: Desktop
Screen.Recording.2024-01-30.at.10.07.08.PM.mov