-
Notifications
You must be signed in to change notification settings - Fork 349
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
Pull out paginators #480
Comments
In general, i think, this is a good idea.. However, this would make the release-process of a new fractal version way more complicated, because you need to keep those packages in-sync.. |
@johannesschobel I agree. But since the paginators (probably) won't change much, it might not be terrible to maintain them. Or even find people who are willing to help us keep up. |
I definitely agree, that it would add a certain level of flexibility.. |
I agree these are best separated out, this was brought up as part of #474.
One thing to remember with releases is that we don't necessarily have to release a new version of the paginators / serializers every time we release a core version. There are option, for example we might want to keep just the major version numbers in sync. |
I've split out the paginators:
Just need to get an |
Im going to close this for now. |
Fractal ships with the following paginators:
I think we should make a basic paginator class, and move these 5 to separate repositories that can be suggested via Composer.
Thoughts?
The text was updated successfully, but these errors were encountered: