Skip to content

CachedTopicRepository Scope #30

Open

Description

@JeremyCaney

Currently, the CachedTopicRepository will load the entire Root topic and all descendants. It will not load any topics outside of the Root topic, nor can it be restricted to a single section of the topic graph.

Consider implementing functionality that allows the scope of the CachedTopicRepository to 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

  • The Root:Configuration is only needed if there's write access, and can otherwise be handled via TopicRepository.
  • The OnTopic Editor will need access to all topics, so editors can maintain the entire tree.
  • In Dependency Injection, constructor parameters should be required, not optional.
  • Should we ever allow topics to be created outside of Root? Or should these always be children of Root?

Proposal: CachedAreaTopicRepository

  • Derives from CachedTopicRepository
  • Exposes a required rootTopicKey constructor parameter
  • Sets a protected string RootTopicKey property

Activity

  1. added
    Area: RepositoriesRelates to the `ITopicRepository` interface or one of its implementations.
    Status 0: DiscussionNeeds further evaluation of requirements and prioritization.
    Type: FeatureIntroduces a major area of functionality.
    on Mar 5, 2021
  2. added this to the OnTopic 5.3.0 milestone on Oct 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Area: RepositoriesRelates to the `ITopicRepository` interface or one of its implementations.Priority: 2Status 0: DiscussionNeeds further evaluation of requirements and prioritization.Type: FeatureIntroduces a major area of functionality.

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions