Context:
PostProcessingAction is documented to facilitate in-memory tranformations or filtering:
https://specification.ardalis.com/features/postprocessingaction.html
Issue:
In a simple scenario we have a Fullname computed property which is built from Firstname and Lastname columns. We use PostProcessingAction to implement filtering functionality on the Fullname.
Our ListAsync call handles this perfectly by filtering the result set correctly. However, our accompanying CountAsync ignores the PostProcessingAction and gives an incorrect totalcount for our paging implementation.
This does seem to be the intended implementation when looking at this: #134 (comment)
Expected result:
ListAsync and CountAsync should resolve to identical result sets. Since PostProcessingAction is documented to facilitate in-memory filtering I expect the CountAsync to also resolve the PostProcessingAction to respect any in-memory filtering implementations to return the correct count.
Context:
PostProcessingActionis documented to facilitate in-memory tranformations or filtering:https://specification.ardalis.com/features/postprocessingaction.html
Issue:
In a simple scenario we have a
Fullnamecomputed property which is built fromFirstnameandLastnamecolumns. We usePostProcessingActionto implement filtering functionality on theFullname.Our
ListAsynccall handles this perfectly by filtering the result set correctly. However, our accompanyingCountAsyncignores thePostProcessingActionand gives an incorrect totalcount for our paging implementation.This does seem to be the intended implementation when looking at this: #134 (comment)
Expected result:
ListAsyncandCountAsyncshould resolve to identical result sets. SincePostProcessingActionis documented to facilitate in-memory filtering I expect theCountAsyncto also resolve thePostProcessingActionto respect any in-memory filtering implementations to return the correct count.