Bart Koelman

I'm surprised by that query layer (assuming it originates from JADNC v5.7.1). I would have expected to see multiple field selectors (one per derived type), with pagination inside them. But...

Well, I suspect the printed `QueryLayer` is from the `CountAsync()` method, not from `GetAsync()`. I've merged a PR that logs both `QueryLayer` and the resulting LINQ expression at Debug level....

@JohnStrim Thanks for the great repro project. It's been very helpful to further analyze what is happening. The PR at https://github.com/JohnStrim/JsonApiBugReport/pull/1 contains a workaround. In case it gets lost, it's...

Hard to say, but I doubt it's much better than what I came up with, which wasn't great either. The good news is I found a better way. See https://github.com/JohnStrim/JsonApiBugReport/pull/2...

The pruner doesn't exist anymore. Did you follow the instructions described in https://github.com/JohnStrim/JsonApiBugReport/pull/2, ie add resource definitions to your project?

Can you sort them in de serialize callback on resource definitions?

Please read up on what I wrote in the comments of both PRs, I don't think you understand what's going on. The goal is to disable pagination only on small...

> We consider this to be a major breaking change Nested pagination is not new. It was introduced five years ago in v4.0 [here](https://github.com/json-api-dotnet/JsonApiDotNetCore/pull/792). There is no major breaking change;...

@JohnStrim I appreciate you're offering to do the work, and I'm not fundamentally against it. However, there are additional costs involved, as it expands the set of feature combinations that...

Thanks. So, if I understand correctly, the model looks like this: ``` PriceList [HasMany] PriceListItem[] Items PriceListItem [HasOne] Product Product ``` First of all, when you proposed an option to...