-
Notifications
You must be signed in to change notification settings - Fork 244
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
Library outdated #410
Comments
No, it is still maintained - I use it in several projects, some of which are on Angular v17. Which version are you having trouble with? |
Thanks for the response. I am using Angular v18. |
ok. please provide all relevant details of any errors you get with v18. I've not tested it yet. |
Here's one that you'll hit when using standalone components:
|
@godenji thanks for the info. So right now you just need to entire If anyone wants to make the necessary changes to make the lib compatible with standalone, please let me know. Otherwise I'll get around to it when I have time. |
Do you mean adding pagination module to Also, on Angular 18 here, so perhaps there are other changes at play; thus the title of this github issue :) p.s. thank you for creating this useful library. |
From the angular.io components docs:
Importing the module into your standalone component should work fine. I'm doing it with this lib on a production v17 app. |
Ah, could be this that I'm hitting:
Looks like I need to fully migrate target route and all of its subcomponents to standalone first (I just attempted to convert pagination component in the hierarchy to standalone and import Hopefully it's as straightforward as that... |
@godenji:- Did you find any alternative solution for this? I am also facing some issue like yours? |
@michaelbromley : Are you planning to migrate it to the latest version(16/17) of the angular? |
I have installed in my V18 app importing the NgxPaginationModule in my components import array, and it works fine, a small problem though as the new @for directive doesn't allow me to add paginate pipe alongside it. so I used the old ngFor directive and its working as expected. |
Has the author stopped supporting this library? Looks like it is not compatible with the latest Angular version.
The text was updated successfully, but these errors were encountered: