Skip to content
New issue

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

Row selector template provided index is not correct #5770

Closed
damyanpetev opened this issue Sep 11, 2019 · 0 comments · Fixed by #5772
Closed

Row selector template provided index is not correct #5770

damyanpetev opened this issue Sep 11, 2019 · 0 comments · Fixed by #5772
Assignees
Labels
🐛 bug Any issue that describes a bug grid: general grid: row-selection version: 8.2.x ✅ status: resolved Applies to issues that have pending PRs resolving them, or PRs that have already merged.

Comments

@damyanpetev
Copy link
Member

Description

The context index provided in the Grid is not correct.

  • igniteui-angular version: 8.2.x
  • browser:

Steps to reproduce

  1. Open the Numbering demo from samples (Add row selectors template samples for all grids igniteui-angular-samples#1368)
  2. Switch to page 2
  3. Observe the row numbers

Result

With every page the index provided jumps ahead of what it should be - with 10 per page starting from 21 on the second page:
image

Expected result

Provided index in the template should be correct.

@damyanpetev damyanpetev added the 🛠️ status: in-development Issues and PRs with active development on them label Sep 11, 2019
jackofdiamond5 added a commit that referenced this issue Sep 11, 2019
@jackofdiamond5 jackofdiamond5 added ✅ status: resolved Applies to issues that have pending PRs resolving them, or PRs that have already merged. and removed 🛠️ status: in-development Issues and PRs with active development on them labels Sep 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛 bug Any issue that describes a bug grid: general grid: row-selection version: 8.2.x ✅ status: resolved Applies to issues that have pending PRs resolving them, or PRs that have already merged.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants