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

DataTable rowIndex in body template is NaN #1929

Closed
ilianiv opened this issue Jan 27, 2017 · 5 comments
Closed

DataTable rowIndex in body template is NaN #1929

ilianiv opened this issue Jan 27, 2017 · 5 comments
Assignees
Labels
Type: Bug Issue contains a bug related to a specific component. Something about the component is not working
Milestone

Comments

@ilianiv
Copy link

ilianiv commented Jan 27, 2017

I'm submitting a ... (check one with "x")

[x] bug report => Search github for a similar issue or PR before submitting
[ ] feature request => Please check if request is not on the roadmap already https://github.com/primefaces/primeng/wiki/Roadmap
[ ] support request => Please do not submit support request here, instead see http://forum.primefaces.org/viewforum.php?f=35

Plunkr Case (Bug Reports)
http://plnkr.co/edit/04PrXG?p=preview

Current behavior
Index of the row is NOT available at the template.

Expected behavior
Index of the row to be available at the template.

Minimal reproduction of the problem with instructions

Try to use let-index="rowIndex"

What is the motivation / use case for changing the behavior?

It does not work

  • Angular version: 2.4.X
  • PrimeNG version: 2.0.0-rc.1
  • Browser: all
@ilianiv
Copy link
Author

ilianiv commented Jan 27, 2017

Maybe this is the same issue #1910

@Emdee89
Copy link

Emdee89 commented Jan 27, 2017

can confirm this. This bug makes new version 2.0 not usable for my project

@Gwiny
Copy link

Gwiny commented Jan 30, 2017

Yes, I have this problem too. Would appreciate fixes.

@shajeeck
Copy link

Update caused this problem! any fix ??

@Emdee89
Copy link

Emdee89 commented Jan 31, 2017

Pull Request 1932 fixes this issue.
#1932

Looking forward to a fix, otherwise migration to PrimeNG 2 is not possible within our project.

@cagataycivici cagataycivici self-assigned this Feb 1, 2017
@cagataycivici cagataycivici added the Type: Bug Issue contains a bug related to a specific component. Something about the component is not working label Feb 1, 2017
@cagataycivici cagataycivici added this to the 2.0-RC3 milestone Feb 1, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Bug Issue contains a bug related to a specific component. Something about the component is not working
Projects
None yet
Development

No branches or pull requests

5 participants