#
#
limit_selector_js_tag
The limit_selector_js_tag allows the user to select any arbitrary limit per page, up to the :requestable_limit option. It raises an OptionError exception if the :requestable_limit is not truthy.
It works with all paginators but :keyset
<%== @pagy.limit_selector_js_tag %>Try this method in the Pagy Console:
>> puts @pagy.limit_selector_js_tag(requestable_limit: 100)
<span class="pagy limit-selector-js" data-pagy="WyJzaiIsNDEsIi9wYXRoP2V4YW1wbGU9MTIzJnBhZ2U9UCAiXQ=="><label>Show <input name="limit" type="number" min="1" max="" value="20" style="padding: 0; text-align: center; width: 3rem;"><a style="display: none;">#</a> items per page</label></span>
=> nil
>> puts @pagy.limit_selector_js_tag(requestable_limit: 100, id: 'my-elector', item_name: 'Products')
<span id="my-elector" class="pagy limit-selector-js" data-pagy="WyJzaiIsNDEsIi9wYXRoP2V4YW1wbGU9MTIzJnBhZ2U9UCAiXQ=="><label>Show <input name="limit" type="number" min="1" max="" value="20" style="padding: 0; text-align: center; width: 3rem;"><a style="display: none;">#</a> Products per page</label></span>
=> nilIt looks like: Show Products per page
Pagy requests the right page number
After selecting a new limit, pagy reloads the page that roughly contains the same items shown before the reload.
Overriding *_js* helpers is not recommended
The *_js* helpers are tightly coupled with the javascript code, so any partial overriding on one side, would be quite fragile
and might break in a next release.