build(deps): bump pagy from 7.0.11 to 9.0.1

[dependabot]

Bumps pagy from 7.0.11 to 9.0.1.

Release notes

Sourced from pagy's releases.

Version 9.0.1

✴ What's new in 9.0+ ✴

• Wicked-fast Keyset Pagination for big data! It works with ActiveRecord::Relation and Sequel::Dataset sets.
• More Playground Apps to showcase, clone and develop pagy APPs without any setup on your side
• Lots of refactorings and optimizations
• See the Changelog for possible breaking changes

Changes in 9.0.1

• Fix countless executing the count query
• Rename row_comparison > tuple_comparison; ignore mixed orders

CHANGELOG

Version 9.0.0

✴ What's new in 9.0+ ✴

• Wicked-fast Keyset Pagination for big data! It works with ActiveRecord::Relation and Sequel::Dataset sets.
• More Playground Apps to showcase, clone and develop pagy APPs without any setup on your side
• Lots of refactorings and optimizations
• See the Changelog for breaking changes

Changes in 9.0.0

• Improve Keyset::Sequel and docs
• BREAKING: Rename :max_limit > :limit_max
• BREAKING: Rename variable, param, accessor, extra and helper "items" to "limit"
• Add playground keyset_ar.ru and keyset_s.ru apps and integration with the rest of the gems
• Add keyset pagination base files
  • Pagy::Keyset API
  • ActiveRecord and Sequel adapters
• BREAKING: Transform the vars positional hash argument in keyword arguments (double splat); internal renaming of setup/assign methods
• Refactor pagy_get_vars in various backend extras
• BREAKING: Refactor the fragment url
• BREAKING: Refactor the anchor_string system
• BREAKING: Drop the support for 8+ deprecations

CHANGELOG

Version 8.6.3

✴ What's new in 8.0+ ✴

• New Pagy Playground to showcase, clone and develop pagy APPs without any setup on your side (try the pagy demo)
• New :max_pages variable to limit the pagination regardless the actual count
• Better frontend helpers

... (truncated)

Changelog

Sourced from pagy's changelog.

Version 9.0.1

• Fix countless executing the count query
• Rename row_comparison > tuple_comparison; ignore mixed orders

Version 9.0.0

Breaking Changes

Dropped support for deprecated stuff

• The foundation, materialize, semantic and uikit CSS extras have been removed: (See the reasons)
• Javascript renamed files
  • pagy.js: use pagy.min.js
  • pagy-module.js: use pagy.mjs
  • pagy-dev.js: use the pagy.min.jswith the pagy.min.js.map
  • pagy-module.d.ts: use pagy.d.ts
• The Array type for the :size (e.g. size: [1, 4, 4, 1]) that generates the classic bar is not supported anymore: use the :size set to an integer with the ends: true variable (which are the default since 8.4.6). If a legacy bar remains REALLY a requirement, add require 'pagy/extras/size to your pagy.rb initalizer. (See the size extra)

Simple renaming

We used items for too many things that confused even maintainers. The "items" are now referencing only the records/elements fetched from a collection (plural entity), so they are kept as before (e.g. pagy_*get_items methods). The "number of items" (singular entity), are now unmistakably referenced as the limit everywhere (code, API, files, extras, docs, etc.). The logic didn't change so you have just to globally search 'items' and replace with limit and you should be done... or use the detailed table below:

Type	Search	Replace
Pagy Variable	:items	:limit
Extra Path	pagy/extras/items	pagy/extras/limit
Extra Variable	:items_param	:limit_param
Default URL param	items	limit
Extra Variable	:items_extra	:limit_extra
Extra Variable	:max_items	:limit_max (now inverted)
Extra Method	pagy_items_selector_js	pagy_limit_selector_js
Extra Variable	:headers[:items]	:headers[limit]

Code changes

• The DEFAULT[:anchor_string] was useless and has been dropped.
• The :anchor_stringand the :fragment are not instance variables anymore, but keyword arguments for all the helpers, because it is frontend code (see the discussion). Instead of passing them to the pagy* method in the controller, pass it to any pagy_*nav method in the view.
• A general internal revamp has changed the positional argument for the Pagy::* objects and constructors methods to keyword arguments. If you get a wrong number of arguments (given 1, expected 0) (ArgumentError), just use a double splat **.

... (truncated)

Commits

• b7bac8d Merge branch 'dev'
• a29d3dc Version 9.0.1
• 01dac53 Update gems
• 6cd6e2f Add missing markers in github file
• 13702b3 Fix countless executing the count query
• 21c70d1 Rename row_comparison > tuple_comparison; ignore mixed orders
• 864baf2 Merge branch 'dev'
• 20f3e12 Version 9.0.0
• ae2cc69 Ensure bump script copies also the "What's new" from README
• 46132a7 Improve Keyset::Sequel and docs
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[dependabot]

Superseded by #1094.