[BUG] Fix record relation optimistic mutation (#9881)
# Introduction It seems like optimistic caching isn't working as expected for any record relation mutation, CREATE UPDATE DELETE. It should not have an impact on the destroy We included a new `computeOptimisticRecordInput` that will calculate if a relation is added or detach. Updated the `triggerCreateRecordsOptimisticEffect` signature we should have a look to each of its call to determine if it should be checking cache or not Related to #9580 --------- Co-authored-by: Charles Bochet <charles@twenty.com>
This commit is contained in:
@ -80,7 +80,11 @@ export const useOpenCreateActivityDrawer = ({
|
||||
setViewableRecordNameSingular(activityObjectNameSingular);
|
||||
|
||||
const activity = await createOneActivity({
|
||||
assigneeId: customAssignee?.id,
|
||||
...(activityObjectNameSingular === CoreObjectNameSingular.Task
|
||||
? {
|
||||
assigneeId: customAssignee?.id,
|
||||
}
|
||||
: {}),
|
||||
position: 'last',
|
||||
});
|
||||
|
||||
|
||||
Reference in New Issue
Block a user