-
Notifications
You must be signed in to change notification settings - Fork 2
Collection integration of Lazy-Loading, especially Topic.Children #119
Copy link
Copy link
Closed
Labels
Area: RepositoriesRelates to the `ITopicRepository` interface or one of its implementations.Relates to the `ITopicRepository` interface or one of its implementations.Priority: 3Severity 1: MinorStatus 5: CompleteTask is considered complete, and ready for deployment.Task is considered complete, and ready for deployment.Type: BugBehavior that is inconsistent with documented or expected behavior.Behavior that is inconsistent with documented or expected behavior.Type: ImprovementImproves the functionality or interface of an existing feature.Improves the functionality or interface of an existing feature.
Milestone
Description
Activity
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: 3Severity 1: MinorStatus 5: CompleteTask is considered complete, and ready for deployment.Task is considered complete, and ready for deployment.Type: BugBehavior that is inconsistent with documented or expected behavior.Behavior that is inconsistent with documented or expected behavior.Type: ImprovementImproves the functionality or interface of an existing feature.Improves the functionality or interface of an existing feature.
Address collection-level issues introduced by lazy loading (#111).
LoadStatehad been added to the genericKeyedTopicCollection<T>, which leaks a the "load state" concept onto non-child collections (e.g., metadata, content-type descriptors) that never need it.Also, formalize documentation warning future
ITopicRepositoryimplementers about the risks of manually settingLoadStateandDeferredincorrectly (i.e., data loss or spurious reloads).ChildTopicCollectionforTopic.Children, and removeLoadStatefrom the generic baseLoadStateandDeferredsetters