I might be missing these methods, or easy implementation but I just can't seem to find them in the documentation and examples.

Removing row by index. - You insert and update row by index, however removing row is suddenly by definite field and value or unique Id. I often missed ability to remove a row by its index instead of having to look for a value in that one specific row so that i can remov

Can this be added to the List API docs please?
As well as the documented:

listObj.search('Jonny'); // Only item with name Jonny is shown (also returns this item)
listObj.search(); // Show all items in list
listObj.search('Jonny', ['name']); // Only search in the 'name' column

search also supports a (currently undocumented) custom search function as the 2nd or 3rd argument:

We've received a good amount of feedback for formatting values instantiated within the page_entries_info method. Currently we don't have a concrete interface for the method and Kaminari users need to implement a decorator that's not intuitive. It would be helpful if the method sends a certain sed of messages to the collection object. I'm not sure what the interface should look like, but here i

Bug description:

Accordion Custom header demo does not follow WAI-ARIA Authoring Practices for accordion.

The title of each accordion header is contained in an element with role button.
Each accordion header button is wrapped in

Currently the pagination shows(with text previous and next) even if the page count is zero. Ideally it should get hidden if the page count is zero.

my app's page params are in the url

things_path(page: 2) # => "/things/page/2"

not

things_path(page: 2) # => "/things?page=2"

however, the generated links use this second form, which appears to be hardcoded in Pagination#_paginate_collection

Hello!

I am using [email protected] and I had a necessity to set selected page number explicitly. I was trying to pass the selected page number in both force-page and initial-page props, but it didn't work. Thanks to Vue devtools, I had found out the value property and successfully used it to determine selected page number. So, please, update the docs and mention the value property

Is your feature request related to a problem? Please describe.
In the documentation you simply pass an IQueryable to the PagedList without any sort of keyselector. However if you e.g. pass an IQueryable from a database without any keyselector, then the results aren't guaranteed.

The generated SQL (For sql server) is as follows

SELECT [a].[WtgId], [a].[TimeOnUtc], [a].[Code], [a]

This is a feature request.

Prerequisites

• Are you running the latest version?
• Are you reporting to the correct repository?
• Did you check the documentation?
• Did you perform a cursory search?

Description

It would be nice to get a config option to set the decimal

Hello,

When I click on 'next' button, it remains hovered until I click somewhere else.

My component calls a getResults() method on page change event, that loads the pagination results (same as the Readme demo).

<pagination :data="laravelData" @pagination-change-page=

Hello! This project is great. Thank you for working on it and maintaining it!

I did run across a potential issue while using Autopages. The documentation says to omit any sections you don't want to enable auto-generation for, but it seems that if you enable it for one, you must explicitly disable it for the other available sections. Apologies if this is intended behavior and I've misread the do

If there are datetime columns that are searchable, it causes that global search operates with these columns.
When some national characters are used (e.g. "ř" ), there is a problem with missing collation in datetime columns:

SQL General error: 1271 Illegal mix of collations for operation 'like'