Hi Abp Zero Support,
Our project is using C2A8. Today we upgraded to 4.10.1, and after upgrade, the AuditLogAppService_Tests.Should_Get_Entity_Changes unit test started failing but I didn't touch that unit test.
Shouldly.ShouldAssertException : entityChangeList.TotalCount
should be
2
but was
0
I checked MajesticTestBaseModule, and found following two lines are uncommented.
Configuration.EntityHistory.IsEnabled = true;
Configuration.EntityHistory.Selectors.Add("ProjectEntities", typeof(User), typeof(Tenant));
Not sure why the entity change capture is not happening.
Any related files to this EntityHistory that I could refer to? Like AuditingHelper/Intercepter to AuditLog...
Thank you,
4 Answer(s)
-
0
Because the abp 4.10.x version of the entity history function has undergone some changes.
Zero has not been upgraded to abp 4.10, it may be upgraded directly to abp 5.0, support asp net core 3.0.
You can temporarily ignore this test method and wait for a new version of zero, and then check the changes to this test method.
-
0
Thank you maliming! But doesn't that mean the Entity Change Capture thing isn't working as expected?
-
0
found the issue:
In aspnetboilerplate/src/Abp/EntityHistory/EntityHistoryHelperBase.cs, it's missing the part checking against EntityHistorySelector:
if (EntityHistoryConfiguration.Selectors.Any(selector => selector.Predicate(entityType))) { return true; }Thank you,
-
0
@aiz The fix is already in progress. https://github.com/aspnetboilerplate/aspnetboilerplate/pull/4953
