Bump pagy from 8.6.3 to 9.0.0

[dependabot[bot]]

Bumps pagy from 8.6.3 to 9.0.0.

Release notes

Sourced from pagy's releases.

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

Changelog

Sourced from pagy's changelog.

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 **.

Possibly breaking overrides

• The internal Pagy protected methods have been renamed and refactored. If you use custom Pagy classes, you may need to search into the code.

... (truncated)

Commits

• 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
• 028559f Improve CHANGELOG
• ef728aa Rename :max_limit > :limit_max
• a76882b Improve/fix the new docs
• 5a13f8b Remove legacy assets
• 8663728 Revert 2a25ed59: pagy_*get_record is back as pagy_*get_items singe it doesn't...
• 04ef5f8 Rename variable, param, accessor, extra and helper "items" to "limit"
• 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 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)

[dependabot[bot]]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.