-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
fix: Update task title without opening the report #32249
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,51 @@ | ||
import Onyx, {OnyxEntry} from 'react-native-onyx'; | ||
import CONST from '@src/CONST'; | ||
import ONYXKEYS from '@src/ONYXKEYS'; | ||
import {Report} from '@src/types/onyx'; | ||
import ReportAction from '@src/types/onyx/ReportAction'; | ||
import * as CollectionUtils from './CollectionUtils'; | ||
import * as Localize from './Localize'; | ||
|
||
const allReports: Record<string, Report> = {}; | ||
Onyx.connect({ | ||
key: ONYXKEYS.COLLECTION.REPORT, | ||
callback: (report, key) => { | ||
if (!key || !report) { | ||
return; | ||
} | ||
const reportID = CollectionUtils.extractCollectionItemID(key); | ||
allReports[reportID] = report; | ||
}, | ||
}); | ||
|
||
/** | ||
* Given the Task reportAction name, return the appropriate message to be displayed and copied to clipboard. | ||
*/ | ||
function getTaskReportActionMessage(actionName: string): string { | ||
switch (actionName) { | ||
case CONST.REPORT.ACTIONS.TYPE.TASKCOMPLETED: | ||
return Localize.translateLocal('task.messages.completed'); | ||
case CONST.REPORT.ACTIONS.TYPE.TASKCANCELLED: | ||
return Localize.translateLocal('task.messages.canceled'); | ||
case CONST.REPORT.ACTIONS.TYPE.TASKREOPENED: | ||
return Localize.translateLocal('task.messages.reopened'); | ||
default: | ||
return Localize.translateLocal('task.task'); | ||
} | ||
} | ||
|
||
function getTaskTitle(taskReportID: string, fallbackTitle = ''): string { | ||
const taskReport = allReports[taskReportID] ?? {}; | ||
// We need to check for reportID, not just reportName, because when a receiver opens the task for the first time, | ||
// an optimistic report is created with the only property – reportName: 'Chat report', | ||
// and it will be displayed as the task title without checking for reportID to be present. | ||
return Object.hasOwn(taskReport, 'reportID') && taskReport.reportName ? taskReport.reportName : fallbackTitle; | ||
} | ||
|
||
function getTaskCreatedMessage(reportAction: OnyxEntry<ReportAction>) { | ||
const taskReportID = reportAction?.childReportID ?? ''; | ||
const taskTitle = getTaskTitle(taskReportID, reportAction?.childReportName); | ||
return Localize.translateLocal('task.messages.created', {title: taskTitle}); | ||
} | ||
Comment on lines
+45
to
+49
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. If Returning empty string enables other other parts of the app to detect failure in getting task created message so we can fallback to other messages. (Coming from #35002) |
||
|
||
export {getTaskReportActionMessage, getTaskTitle, getTaskCreatedMessage}; |
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -16,6 +16,7 @@ import * as PersonalDetailsUtils from '@libs/PersonalDetailsUtils'; | |
import ReportActionComposeFocusManager from '@libs/ReportActionComposeFocusManager'; | ||
import * as ReportActionsUtils from '@libs/ReportActionsUtils'; | ||
import * as ReportUtils from '@libs/ReportUtils'; | ||
import * as TaskUtils from '@libs/TaskUtils'; | ||
import * as Download from '@userActions/Download'; | ||
import * as Report from '@userActions/Report'; | ||
import * as Task from '@userActions/Task'; | ||
|
@@ -258,15 +259,13 @@ export default [ | |
type === CONTEXT_MENU_TYPES.REPORT_ACTION && !ReportActionsUtils.isReportActionAttachment(reportAction) && !ReportActionsUtils.isMessageDeleted(reportAction), | ||
|
||
// If return value is true, we switch the `text` and `icon` on | ||
// `ContextMenuItem` with `successText` and `successIcon` which will fallback to | ||
// `ContextMenuItem` with `successText` and `successIcon` which will fall back to | ||
// the `text` and `icon` | ||
onPress: (closePopover, {reportAction, selection}) => { | ||
const isTaskAction = ReportActionsUtils.isTaskAction(reportAction); | ||
const isCreateTaskAction = ReportActionsUtils.isCreatedTaskReportAction(reportAction); | ||
const isReportPreviewAction = ReportActionsUtils.isReportPreviewAction(reportAction); | ||
const message = _.last(lodashGet(reportAction, 'message', [{}])); | ||
const reportID = lodashGet(reportAction, 'originalMessage.taskReportID', '').toString(); | ||
const messageHtml = isTaskAction || isCreateTaskAction ? Task.getTaskReportActionMessage(reportAction.actionName, reportID, isCreateTaskAction) : lodashGet(message, 'html', ''); | ||
const messageHtml = isTaskAction ? Task.getTaskReportActionMessage(reportAction) : lodashGet(message, 'html', ''); | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Hi, it looks like this method was moved to
|
||
|
||
const isAttachment = ReportActionsUtils.isReportActionAttachment(reportAction); | ||
if (!isAttachment) { | ||
|
@@ -281,6 +280,9 @@ export default [ | |
} else if (ReportActionsUtils.isMoneyRequestAction(reportAction)) { | ||
const displayMessage = ReportUtils.getIOUReportActionDisplayMessage(reportAction); | ||
Clipboard.setString(displayMessage); | ||
} else if (ReportActionsUtils.isCreatedTaskReportAction(reportAction)) { | ||
const taskPreviewMessage = TaskUtils.getTaskCreatedMessage(reportAction); | ||
Clipboard.setString(taskPreviewMessage); | ||
} else if (ReportActionsUtils.isChannelLogMemberAction(reportAction)) { | ||
const logMessage = ReportUtils.getChannelLogMemberMessage(reportAction); | ||
Clipboard.setString(logMessage); | ||
|
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 basically line-to-line duplicate of this block, and maybe others.
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.
Yup. I once had a somewhat similar question, and this was the response from @tgolen:
I may not be aware, is there a way to reuse the
Onyx.connect
?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.
I don't know, maybe
ReportUtils.getReportById
or something like that? It seems werid to just copy-paste this because there "hasn't been a problem yet"...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.
@tgolen what would you say? Can we reuse utils inside other utils instead of using
Onyx.connect
?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.
That is a very nuanced topic, so I apologize in advance for the long comment, but I want you to hear my thinking.
There is no technical problem with having the same
connect()
in two different libs. The only "problem" is that it is repetitive code, which is a somewhat valid argument. However, let's take that logic all the way to the grand conclusion. If we only intend to have oneconnect()
for every key, then that basically results in some kind of file that contains all theconnect()
calls for every key. This then creates an odd in-memory type store of everything that Onyx already has in memory. This is just a strange place to end up in.Having duplicate
connect()
s in the files that need them allows them to be custom-tailored for fast lookups or custom maps depending on what data is being accessed. For example, rather than doing a.filter()
or.map()
every time the data needs accessed, theconnect()
callback should store the data in an efficient way so that it can be easily and quickly accessed likereports[reportID]
and there is no need to filter or map. This allows for code to be much more optimized, rather than kept in a very general and slow method (because it has to account for different libs wanting to access it in different ways).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.
Thanks, this makes sense in terms of productivity vs clean code.
Based on the comment above, should we be good to go with this approach @cubuspl42?
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 doesn't make sense, at least to me.
Code duplication is an industry-standard problem with industry-standard solutions.
Even more precisely, even the duplication of data access code is industry-standard, this has been present since the old days of hand-crafted MPA DAOs written in PHP, Java, or whatever. The only twist is the data is reactive here, changing as the time flows.
We've discussed the "big picture", the general case, but coming down to our case, the only argument I can hear for not de-duplicating this is "this might be optimized in the future, so let's keep the duplication", which falls into the YAGNI category for me.
Having said all this, it's not a blocker for me, as I'm kind of busy and can't afford discussing this too much.