-
Notifications
You must be signed in to change notification settings - Fork 2
CachedTopicRepository Scope #30
Copy link
Copy link
Open
Labels
Area: RepositoriesRelates to the `ITopicRepository` interface or one of its implementations.Relates to the `ITopicRepository` interface or one of its implementations.Priority: 2Status 0: DiscussionNeeds further evaluation of requirements and prioritization.Needs further evaluation of requirements and prioritization.Type: FeatureIntroduces a major area of functionality.Introduces a major area of functionality.
Milestone
Metadata
Metadata
Assignees
Labels
Area: RepositoriesRelates to the `ITopicRepository` interface or one of its implementations.Relates to the `ITopicRepository` interface or one of its implementations.Priority: 2Status 0: DiscussionNeeds further evaluation of requirements and prioritization.Needs further evaluation of requirements and prioritization.Type: FeatureIntroduces a major area of functionality.Introduces a major area of functionality.
Currently, the
CachedTopicRepositorywill load the entireRoottopic and all descendants. It will not load any topics outside of theRoottopic, nor can it be restricted to a single section of the topic graph.Consider implementing functionality that allows the scope of the
CachedTopicRepositoryto be restricted to a particular area. This would allow e.g. subdomains to load just a segment of the tree without needing access to the entire tree.Considerations
Root:Configurationis only needed if there's write access, and can otherwise be handled viaTopicRepository.Root? Or should these always be children ofRoot?Proposal:
CachedAreaTopicRepositoryCachedTopicRepositoryrootTopicKeyconstructor parameterprotected string RootTopicKeyproperty