From 45101b5a0947effa188aecddfeb095eb4e53e8ab Mon Sep 17 00:00:00 2001 From: Erik-Jan Westendorp Date: Thu, 2 Jan 2025 07:22:55 +0100 Subject: [PATCH 1/4] Write shorter sentences --- .../customizing/foundation/working-with-data/repositories.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/15/umbraco-cms/customizing/foundation/working-with-data/repositories.md b/15/umbraco-cms/customizing/foundation/working-with-data/repositories.md index 1998828021c..a37f12880f4 100644 --- a/15/umbraco-cms/customizing/foundation/working-with-data/repositories.md +++ b/15/umbraco-cms/customizing/foundation/working-with-data/repositories.md @@ -20,12 +20,12 @@ const repositoryManifest = { }; ``` -With a repository we can have different data sources depending on the state of the app. It can be from a server, an offline database, a store, a Signal-R connection, etc. That means that the consumer will not have to be concerned how to access the data, add or remove items from a collection of items, etc. This means we get a loose connection between the consumer and the data-storing procedures hiding all complex implementation. +With a repository we can have different data sources depending on the state of the app. It can be from a server, an offline database, a store, a Signal-R connection, etc. That means that the consumer will not have to be concerned how to access the data, add or remove items from a collection, etc. This means we get a loose connection between the consumer and the data-storing procedures hiding all complex implementation. ### Data flow with a repository

Data flow

-A repository has to be instanced in the context where it is used. It should take a host element as part of the constructor, so any contexts consumed in the repository (notifications, modals, etc.) get rendered in the correct DOM context. +A repository has to be instanced in the context where it is used. It should take a host element as part of the constructor. This ensures that any contexts consumed in the repository, like notifications or modals, are rendered in the correct DOM context. A repository can be called directly from an element, but will often be instantiated in a context, like the Workspace Context. From 24088dad742ac6e5bd5fb251141a9a1102d4f41c Mon Sep 17 00:00:00 2001 From: Erik-Jan Westendorp Date: Thu, 2 Jan 2025 07:25:06 +0100 Subject: [PATCH 2/4] Update v14 --- .../customizing/foundation/working-with-data/repositories.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/14/umbraco-cms/customizing/foundation/working-with-data/repositories.md b/14/umbraco-cms/customizing/foundation/working-with-data/repositories.md index 1998828021c..a37f12880f4 100644 --- a/14/umbraco-cms/customizing/foundation/working-with-data/repositories.md +++ b/14/umbraco-cms/customizing/foundation/working-with-data/repositories.md @@ -20,12 +20,12 @@ const repositoryManifest = { }; ``` -With a repository we can have different data sources depending on the state of the app. It can be from a server, an offline database, a store, a Signal-R connection, etc. That means that the consumer will not have to be concerned how to access the data, add or remove items from a collection of items, etc. This means we get a loose connection between the consumer and the data-storing procedures hiding all complex implementation. +With a repository we can have different data sources depending on the state of the app. It can be from a server, an offline database, a store, a Signal-R connection, etc. That means that the consumer will not have to be concerned how to access the data, add or remove items from a collection, etc. This means we get a loose connection between the consumer and the data-storing procedures hiding all complex implementation. ### Data flow with a repository

Data flow

-A repository has to be instanced in the context where it is used. It should take a host element as part of the constructor, so any contexts consumed in the repository (notifications, modals, etc.) get rendered in the correct DOM context. +A repository has to be instanced in the context where it is used. It should take a host element as part of the constructor. This ensures that any contexts consumed in the repository, like notifications or modals, are rendered in the correct DOM context. A repository can be called directly from an element, but will often be instantiated in a context, like the Workspace Context. From d1ff6e58372d06bda484b3ab9b8d1518608d89d8 Mon Sep 17 00:00:00 2001 From: Erik-Jan Westendorp Date: Mon, 6 Jan 2025 16:28:24 +0100 Subject: [PATCH 3/4] Update 14/umbraco-cms/customizing/foundation/working-with-data/repositories.md Co-authored-by: sofietoft --- .../customizing/foundation/working-with-data/repositories.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/14/umbraco-cms/customizing/foundation/working-with-data/repositories.md b/14/umbraco-cms/customizing/foundation/working-with-data/repositories.md index a37f12880f4..b094f93569e 100644 --- a/14/umbraco-cms/customizing/foundation/working-with-data/repositories.md +++ b/14/umbraco-cms/customizing/foundation/working-with-data/repositories.md @@ -20,7 +20,7 @@ const repositoryManifest = { }; ``` -With a repository we can have different data sources depending on the state of the app. It can be from a server, an offline database, a store, a Signal-R connection, etc. That means that the consumer will not have to be concerned how to access the data, add or remove items from a collection, etc. This means we get a loose connection between the consumer and the data-storing procedures hiding all complex implementation. +With a repository we can have different data sources depending on the state of the app. The data sources can come from places like a server, an offline database, a store, or a Signal-R connection. That means that the consumer will not have to be concerned how to access the data, add or remove items from a collection, etc. This means we get a loose connection between the consumer and the data-storing procedures hiding all complex implementation. ### Data flow with a repository From 620f4a9ab2143901bab9db78a32784bf9ae25774 Mon Sep 17 00:00:00 2001 From: Erik-Jan Westendorp Date: Mon, 6 Jan 2025 16:32:24 +0100 Subject: [PATCH 4/4] Update v15 --- .../customizing/foundation/working-with-data/repositories.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/15/umbraco-cms/customizing/foundation/working-with-data/repositories.md b/15/umbraco-cms/customizing/foundation/working-with-data/repositories.md index a37f12880f4..b094f93569e 100644 --- a/15/umbraco-cms/customizing/foundation/working-with-data/repositories.md +++ b/15/umbraco-cms/customizing/foundation/working-with-data/repositories.md @@ -20,7 +20,7 @@ const repositoryManifest = { }; ``` -With a repository we can have different data sources depending on the state of the app. It can be from a server, an offline database, a store, a Signal-R connection, etc. That means that the consumer will not have to be concerned how to access the data, add or remove items from a collection, etc. This means we get a loose connection between the consumer and the data-storing procedures hiding all complex implementation. +With a repository we can have different data sources depending on the state of the app. The data sources can come from places like a server, an offline database, a store, or a Signal-R connection. That means that the consumer will not have to be concerned how to access the data, add or remove items from a collection, etc. This means we get a loose connection between the consumer and the data-storing procedures hiding all complex implementation. ### Data flow with a repository