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

rowsPerPageOptions dropdown is not coming in Paginator #159

Closed
Deepak2985 opened this issue Jan 25, 2020 · 4 comments
Closed

rowsPerPageOptions dropdown is not coming in Paginator #159

Deepak2985 opened this issue Jan 25, 2020 · 4 comments
Assignees
Labels
Type: Bug Issue contains a bug related to a specific component. Something about the component is not working
Milestone

Comments

@Deepak2985
Copy link

image

Even after adding these input properties to datatable the rowsPerPageOptions dropdown is not coming and I am getting the warning as in the above screenshot.
:paginator="true"
:rows="10"
:rowsPerPageOptions="[10,20,30]"

@cagataycivici cagataycivici self-assigned this Jan 28, 2020
@cagataycivici cagataycivici added the Type: Enhancement Issue contains an enhancement related to a specific component. Additional functionality has been add label Jan 28, 2020
@cagataycivici cagataycivici added this to the 1.0.2 milestone Jan 28, 2020
@cagataycivici cagataycivici added Type: Bug Issue contains a bug related to a specific component. Something about the component is not working Status: Discussion Issue or pull request needs to be discussed by Core Team and removed Type: Enhancement Issue contains an enhancement related to a specific component. Additional functionality has been add Type: Bug Issue contains a bug related to a specific component. Something about the component is not working Status: Discussion Issue or pull request needs to be discussed by Core Team labels Jan 28, 2020
@cagataycivici cagataycivici changed the title rowsPerPageOptions dropdown is not coming in Datatable rowsPerPageOptions dropdown is not coming in Paginator Jan 30, 2020
@Deepak2985
Copy link
Author

@cagataycivici Thank you for such an early fixing of issue. I really appreciate that. 🙂

@Deepak2985
Copy link
Author

@cagataycivici I am get the similar error even after pulling the new version 1.0.2

image

@fairking
Copy link

Sometimes I got some errors after upgrading a new version. Try to clear the node_modules folder and run npm install. It looks like some old stuff still remains in the cache. After this all errors disappear.

@Deepak2985
Copy link
Author

@fairking Thank you It worked after removing the node_modules. Earlier I was just removing the primevue folder from node_modules but it didn't work.

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

3 participants