You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: 17/umbraco-cms/customizing/foundation/repositories/README.md
+12-8Lines changed: 12 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -33,33 +33,32 @@ Often, you will find that data is already available and observable in a [context
33
33
34
34
When a context with the appropriate data state is not available, reaching for a repository will ensure access to the needed data no matter the current application state.
35
35
36
-
In the example below, we instantiate the `UmbDocumentItemRepository` directly in a custom element to request Document data by its unique key.
36
+
In the example below, we instantiate the `UmbDocumentItemRepository` directly in a custom element to request Document Item data by its unique key.
Alternatively, you can instantiate the repository in a [controller](..) or [context](../../context-api/README.md), store it in a [state](../states.md), and then consume that context in your element. This is often the preferred approach as it allows for better separation of concerns and reusability across different components.
57
+
Alternatively, you can instantiate the repository in a [controller](..) or [context](../../context-api/README.md), store it in a [state](../states.md), and then use that state in your element. This is often the preferred approach as it allows for better separation of concerns and reusability across different components.
0 commit comments