-
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
[HOLD for payment 2024-06-28] [HOLD for payment 2024-06-24] [HOLD Mentions v2] Support mentions in editing comments #39550
Comments
Triggered auto assignment to @MitchExpensify ( |
|
Held on #39549 |
Hi, I'm Marcin from Software Mansion and I would like to work on this :) |
Sounds good. Just FYI, the back-end for this hasn't been done yet. |
@puneetlath any update on the backend? I think my PR works as expected but would like to get confirmation from your side :) |
Not yet! Will probably be a few more days before I can start the back-end. Are you ready for a review? |
Yup, already marked PR as ready for review, but I wonder if the backend is a blocker for this 🤔 If not I'll notify the reviewer :) |
@puneetlath kind bump :) |
Does it work without the back-end? Like when you refresh the page, is it still shown as mentions? |
@puneetlath Yup, you can see it here or in the PR description :) Screen.Recording.2024-05-13.at.13.10.39.mov |
@war-in are you aware of some "Cannot read properties of undefined (reading ' |
@Beamanator could you give me some details? 🙏 And is it in my PR or do people generally see this error in the app? |
Putting all the details in slack here https://expensify.slack.com/archives/C04878MDF34/p1715699038416249 please @war-jump there if you can, as this is breaking the app in production |
@puneetlath @Beamanator mentioned issue will be resolved in this PR. Can I mark mine as ready for review? I've shown here that it works without the backend |
Yes, sounds good for me. Let's get it in review. |
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results. If a regression has occurred and you are the assigned CM follow the instructions here. If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future. |
@rlinoz mind confirming that we're all done here? |
Let's wait until it gets deployed to prod, but also we might have a case we didn't account for #42521 (comment) |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.84-3 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2024-06-24. 🎊 For reference, here are some details about the assignees on this issue:
|
BugZero Checklist: The PR adding this new feature has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
|
@eh2077 was the C+ |
Payment summary:
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.85-7 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2024-06-28. 🎊 For reference, here are some details about the assignees on this issue: |
BugZero Checklist: The PR adding this new feature has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
|
@rlinoz, @MitchExpensify, @war-in, @eh2077 Whoops! This issue is 2 days overdue. Let's get this updated quick! |
Payment Summary
BugZero Checklist (@MitchExpensify)
|
Checklist
Regression test
Do we agree 👍 or 👎 |
@rlinoz, @MitchExpensify, @war-in, @eh2077 Still overdue 6 days?! Let's take care of this! |
@eh2077 Upwork job created here: https://www.upwork.com/jobs/~012066a1fb40a4a923, offer sent! |
Paid and contract ended |
We want to update the edit comment flow to support editing/adding mentions. This does not mean adding support for the auto-complete component. Just parsing the mentions in both directions. This means that when someone goes to edit a comment with a user or report mention we should:
This is covered in the mentions v2 design doc here.
HOLD for #39549
Issue Owner
Current Issue Owner: @MitchExpensifyThe text was updated successfully, but these errors were encountered: