We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi.
When on first page result, the current link for 1st page has no "current" class applied.
Found this in Pages.cs 81 line
if (i == currentPage || (currentPage <= 0 && i == 0)) { model.PaginationLinks.Add(new PaginationLink { Active = true, PageIndex = i, IsCurrent = true, DisplayText = i.ToString() }); }
Changed to
if (i == currentPage || (currentPage <= 0 && i == 1))
Works, but don't know if it is the right place to fix it.
The text was updated successfully, but these errors were encountered:
Looks like a bug indeed, but it probably never got noticed because it only happens when currentPage is 0 and this doesn't happen in the demos.
Sorry, something went wrong.
ROTFL, but happens on every production page, when you have the first page.
Do you created it for usage in demos only?
Set IsCurrent of first page number link to true when currentPage is n…
746b8c5
…ot set. Fixes issue #33.
No branches or pull requests
Hi.
When on first page result, the current link for 1st page has no "current" class applied.
Found this in Pages.cs 81 line
if (i == currentPage || (currentPage <= 0 && i == 0))
{
model.PaginationLinks.Add(new PaginationLink { Active = true, PageIndex = i, IsCurrent = true, DisplayText = i.ToString() });
}
Changed to
if (i == currentPage || (currentPage <= 0 && i == 1))
Works, but don't know if it is the right place to fix it.
The text was updated successfully, but these errors were encountered: