Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Commit-Queue | +1 |
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Code-Review | +1 |
return;
When is this going to happen? Maybe a comment that this is unexpected edge case?
Thread(thread_type, server_id, "", conversation_turn_id));
comment for this param /*param_name=*/
tasks_.insert_or_assign(task.GetTaskId(), task);
This should be before notifying observers? In case they make a GetTask(..) call..
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
When is this going to happen? Maybe a comment that this is unexpected edge case?
Done
Thread(thread_type, server_id, "", conversation_turn_id));
comment for this param /*param_name=*/
Done
This should be before notifying observers? In case they make a GetTask(..) call..
this notify is a post task, so it will always be executed later. But changed the code to put the insert_or_assign call into the if-else statement.
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Code-Review | +1 |
tasks_.insert_or_assign(task.GetTaskId(), task);
This is common to both blocks.
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
tasks_.insert_or_assign(task.GetTaskId(), task);
This is common to both blocks.
Yes, but I cannot do it before the if statement since the that will make the if statement always return true. Alternatively, I can introduce a temporary variable to store tasks_.find(task.GetTaskId()) == tasks_.end(), and then use that variable later after the insert_or_assign call. But i think the current code is probably better for understanding.
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |