Expose Arrival and Departure collections from EntityLifecycleStatus as ACV interfaces.
What is the current behaviour?
Reading arrival and departure entities from EntityLifecycleStatus within a Task Driver job is cumbersome because the acquisition API doesn't conform to an ACV interface.
What is the new behaviour?
Arrival and Departure lookups are exposed as IReadAccessControlledValue<NativeList<Entity>> getters.
What issues does this resolve?
None
What PRs does this depend on?
None
Does this introduce a breaking change?
[x] Yes
[ ] No
Any use of the arrivals and departures collections will need to be adapted to use the new getters. The conversion should be familiar as they're just exposed ACVs
Ex: entityStatus.AcquireArrivalsAsync(out var myList) -> entityStatus.ArrivedEntities.AcquireReadAsync(out var myList)
Expose Arrival and Departure collections from
EntityLifecycleStatusas ACV interfaces.What is the current behaviour?
Reading arrival and departure entities from
EntityLifecycleStatuswithin a Task Driver job is cumbersome because the acquisition API doesn't conform to an ACV interface.What is the new behaviour?
Arrival and Departure lookups are exposed as
IReadAccessControlledValue<NativeList<Entity>>getters.What issues does this resolve?
What PRs does this depend on?
Does this introduce a breaking change?
Any use of the arrivals and departures collections will need to be adapted to use the new getters. The conversion should be familiar as they're just exposed ACVs Ex:
entityStatus.AcquireArrivalsAsync(out var myList)->entityStatus.ArrivedEntities.AcquireReadAsync(out var myList)