2.0.0 (2019-05-09)
ILoadLinker
methods are now async (#3) (d97d67f)- The signature of
IReferenceLoader.LoadReferencesAsync
has changed.ILookupIdsContext
has been replaced byILoadingContext
. It is now the only parameter forLoadReferencesAsync
and is used for both getting the IDs to lookup and for adding loading references.
- Reference types that are part of a cycle are loaded in multiple batches.
- The overload of
LoadLinkProtocolForLinkedSourceBuilder.LoadLinkReferenceById
for lists has been renamedLoadLinkReferencesByIds
. - The overload of
LoadLinkProtocolForLinkedSourceBuilder.LoadLinkNestedLinkedSourceById
for lists has been renamedLoadLinkNestedLinkedSourcesByIds
. - The overload of
LoadLinkProtocolForLinkedSourceBuilder.LoadLinkNestedLinkedSourceFromModel
for lists has been renamedLoadLinkNestedLinkedSourcesFromModels
. LoadLinkProtocolForLinkedSourceBuilder.PolymorphicLoadLink
has been renamedLoadLinkPolymorphic
.LoadLinkProtocolForLinkedSourceBuilder.PolymorphicLoadLinkForList
has been renamedLoadLinkPolymorphicList
.- Added method
ILoadLinker.EnabledDebugMode()
in order to aid in diagnosing load-link operations (#8).
- Dependency cycles are allowed, except between linked sources of the same type. In other words, there can be a cycle that includes linked sources with the same model type, but cycles with the exact same linked source type is not permitted.
- Reference types can be loaded directly using
ILoadLinkProtocol.Load<TModel>().ByIdAsync({id})
orILoadLinkProtocol.Load<TModel>().ByIdsAsync({ids})
.
In the repository, there is a migration helper.
Copy the file to get help migrating your code. It includes stubs of all the removed classes
and methods (as extension methods), with the ObsoleteAttribute
explaining what to replace them with.
Your build result will include warnings for every use of those classes/methods.