mislav/will_paginate

Pagination library for Rails and other Ruby applications

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 58 minutes ago
Type:Library / SDKCategory(s):Backend FrameworksWeb Development
Added to GitGenius on September 11th, 2026
Created on February 25th, 2008
Open Issues & Pull Requests: 46 (+0)
GitHub issues: Enabled
Number of forks: 856
Total Stargazers: 5,682 (+0)
Total Subscribers: 69 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 50.8 days
Mean response time: 67.5 days
90th percentile: 147.6 days
Tracked items: 3

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 3
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 2,983 days
Stale 30+ days: 3
Stale 90+ days: 3

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • todo (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

will_paginate is a pagination library for Rails and other Ruby applications.

The tool addresses the common need to break large result sets into manageable pages. It provides a straightforward approach by offering helper methods that integrate with Rails views and controllers, allowing developers to paginate database queries and render pagination controls with minimal code. The library handles the calculation of offsets, limits, and page numbers automatically, reducing boilerplate in applications that need to display paginated content.

The tool suits Rails applications and other Ruby projects that require standard pagination functionality. It works with multiple frameworks and data sources, supporting Rails, Sinatra, and Sequel alongside ActiveRecord. Developers building web applications with straightforward pagination needs will find it a practical choice, though those requiring highly customized pagination behavior or working exclusively with modern JavaScript-heavy frontends may need to evaluate whether the view-helper approach aligns with their architecture.

The project maintains steady engagement with its codebase, accepting pull requests that address reported issues and expand compatibility. Development activity shows responsiveness to community contributions, with maintainers reviewing and merging changes that improve the library's functionality across different Ruby frameworks and versions.