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
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 requiredrootTopicKey constructor parameter
Activity