Forest
Forest
You would think that rel next/prev on the actual links would be good enough, but not so according to Google. http://googlewebmastercentral.blogspot.com/2011/09/pagination-with-relnext-and-relprev.html Here is an example from kaminari. https://github.com/amatsuda/kaminari/pull/200/files
I can see how in your case that is not the desired behavior. I don't think it is right to build in knowledge of the eager loading in the client....
Did you try setting it to 0? I think there is an issue with the dirty tracking that doesn't handle nil correctly. This is just a guess. I need to...
@amalagaura I'm happy to take your recommendation and fix for this. I'm no longer actively using this gem and so don't have the time to dig deep on these kinds...
I haven't started on it and welcome prs. On Thu, Sep 7, 2017 at 11:22 PM Tim Brandes wrote: > Dear forest, > > thanks for creating this integration, well...
:+1: I am using a combination of the above to use my application layout and route helpers for my jekyll blog.
@michaelimstepf I'm having the same issue. Did you find a solution to this?
@michaelimstepf thanks for the reply. If I just needed this for one attribute on one class I'd go this route. I opted for this https://gist.github.com/657fd558a9c05416cf81 temporary solution until #209 lands...
@mherold your analysis and solution sounds right. I knew changing `NullifyBlank` wasn't the right solution. :) I'm happy to test with my use case when you push up the PR.