-
-
Notifications
You must be signed in to change notification settings - Fork 13
Description
I would like to be able to assert in unit tests which columns (eg. the expression(s) and its sort direction(s)) are configured on the KeysetPaginationBuilder<T>. But currently the builder its Columns property is internal everywhere (also on the KeysetPaginationContext, as is the KeysetColumn<T> type.
Can we selectively make some of this public? I'd understand you want to avoid exposing too much to keep the API surface small, but tests require too much setup because I have to run the complete query logic, and am effectively writing integration tests. For small unit tests, I do not care and just want to verify that the columns used is correct. I do not really see any downsides of exposing the column expression and direction?
I could also extract it with an expression visitor but this is way too cumbersome and I'd still have to build the entire query (which in my use case is not relevant). Or do you have another recommendation?