From e8fa36a3801ff7eb823b5e10a6cc79fae620b76e Mon Sep 17 00:00:00 2001 From: Josh <37798644+joshuaellis@users.noreply.github.com> Date: Wed, 18 Jan 2023 08:42:31 +0000 Subject: [PATCH] Update docs/docs/core/content-manager/relations.mdx --- docs/docs/core/content-manager/relations.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docs/core/content-manager/relations.mdx b/docs/docs/core/content-manager/relations.mdx index ef7457d0fc..e753dc8edb 100644 --- a/docs/docs/core/content-manager/relations.mdx +++ b/docs/docs/core/content-manager/relations.mdx @@ -126,7 +126,7 @@ data for the api. ### Cleaning data to be posted to the API -The API to update the entiy expects relations to be categorised into two groups, a `connect` array and `disconnect` array. +The API to update the entity expects relations to be categorised into two groups, a `connect` array and `disconnect` array. You could do this as the user interacts with the input but we found this to be confusing and then involved us managing three different arrays which makes the code more complex. Instead, because the browser doesn't really care about whats new and removed and we have a copy of the slice of data we're mutating from the server we can run a small diff algorithm to determine which