-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Rename property of pagination page object to be more intuitive #13492
Comments
I agree with these changes, it will make things a bit more logical I think. We can implement this right now for the next minor release but we will need to keep both versions available to keep backwards compatibility for 4.0 version as well. We can deprecate the old properties after 4.0. In summary:
|
@phalcon/core-team Thoughts? |
Overall i agree. If we are going to release next minor version then we can add new methods. |
Implemented |
I propose changing
before
property ofpage
object toprevious
which is far more intuitive for given context, asbefore
goes better withafter
, notnext
.I know this is minor and breaks BC, but maybe we can do it in 4.0? Or for some time, allow both properties.
EDIT: I also think that having
total_pages
andlast
is a bit redundant. I propose removinglast
.EDIT2: I'd also rename
$paginator->getPaginate()
to either$paginator->getPage()
or$paginator->paginate()
for the same reason - being more intuitive.The text was updated successfully, but these errors were encountered: