diff --git a/src/Umbraco.Web.UI.Client/public-assets/docs/data-flow.svg b/src/Umbraco.Web.UI.Client/public-assets/docs/data-flow.svg new file mode 100644 index 0000000000..e7a8481c17 --- /dev/null +++ b/src/Umbraco.Web.UI.Client/public-assets/docs/data-flow.svg @@ -0,0 +1,19 @@ + + + + + + + + + + + + + + + + + + + diff --git a/src/Umbraco.Web.UI.Client/src/stories/extending/repositories.mdx b/src/Umbraco.Web.UI.Client/src/stories/extending/repositories.mdx index d3e1f3f47e..7d36cf6978 100644 --- a/src/Umbraco.Web.UI.Client/src/stories/extending/repositories.mdx +++ b/src/Umbraco.Web.UI.Client/src/stories/extending/repositories.mdx @@ -26,7 +26,7 @@ With a repository we can have different data sources depending on the state of t ## Data flow with a repository -TODO: add image of 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.