Would this rely on this PR or is the library sufficiently divergent?

Would this rely on this PR or is the library sufficiently divergent?

@wesharper It does, I pinged the author of the PR. Of course there's nothing preventing me from implementing it on this gem before the PR is done, but I think it would violate the spirit of FOSS collaboration.

Of course there's nothing preventing me from implementing it on this gem before the PR is done, but I think it would violate the spirit of FOSS collaboration.

@ellnix totally agree here. Happy to support any way I can, we've been antsy to start using this!

@ellnix The PR has been completed! 🎉 I'm really looking forward to this feature, but I don’t want to rush anyone. Do you have any estimate on when the adjustment for the separate federated search path will be made?

@pozelli probably today, I can't say when it will get merged though.

@pozelli probably today, I can't say when it will get merged though.

@ellnix Thank you so much. From what I'm seeing, I think this can solve my problem, which is caused by having only one pagination for each model. If I force the non-federated multi-search results to be an array (to_a), there will be cases where the pages won't fit properly. I need a single pagination for different models - that is, the federated search.

@ellnix Hi! Hope you are well. Will FederatedSearchResult support pagination backends?

For example, I added the following methods to the class:

def last_page?
    (@metadata['offset'] + @metadata['limit']) >= @metadata['estimatedTotalHits']
end

def out_of_range?
    @metadata['offset'] >= @metadata['estimatedTotalHits']
end

@pozelli

I will look into it right now, the endpoint doesn't support the regular pagination options that search does, but I will look into what I can do to add Kaminari and will_paginate support.