Mislav Marohnić

Thanks for all the info. I will try to work around the bug. The current test suite doesn't have polymorphic associations, so this went undetected.

Hey! That would be valid use if we didn't have actual hyperlinks with rel="prev/next", which we have for a long time now each time you generate pagination with `will_paginate()`. Per...

Not that I know of. The solution would require a separate will_paginate helper method to generate the `` tags, as well as a method to inject those in the current...

Alright, gonna reopen this and anyone is welcome to take a stab at the implementation.

Likely fixed by #372 just the other day. No release yet, though. Can you temporarily upgrade will_paginate in your Gemfile to version from git master branch and see if it...

Thank you for the suggestion! That's not a bad idea. I just hope that `@template.request.query_parameters` is sufficiently equivalent to `@template.params` for GET requests so that this change doesn't cause any...

@malteschmitz Thank you for doing the research! I haven't had time to work on this library much lately, so a PR to address this would be much appreciated

@emclab Did you solve your problem? It's probably a routing issue in your app, and most likely not a bug with will_paginate.

For GitHub, instead of redirecting back to either `127.0.0.1` or `localhost`, GCM should switch to implementing the [Device Authorization Flow](https://docs.github.com/en/developers/apps/building-oauth-apps/authorizing-oauth-apps#device-flow). The benefits are that the completed browser flow does not...

@hickford Thanks for the info! I was able to opt into Device flow by doing this: ``` git config --global credential.gitHubAuthModes device ``` My next question is, why hasn't GCM...