You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It has been pointed out to me that the terminology of certain features of this library is not optimal, especially when you learned about typical MVP patterns somewhere.
Things like instance and controller mean different things there.
My proposal would be the following:
resource stays the same
instance gets renamed to pager
We'll get rid of controller altogether, this can be just resource (it would reflect the relationship to resource better anyway)
Here's an example of how the resource would look like:
import{createResource,resource}from'vuex-pagination'letresource=createResource('books',fetchBooksPage)// returns the same as this:letresource=resource('books')
Let me know what you think!
The text was updated successfully, but these errors were encountered:
controller has been renamed to resource in 1.3.0 but controller will continue to work while we're on the v1.x. In a next minor version, the use of controller will throw a deprecated warning.
It has been pointed out to me that the terminology of certain features of this library is not optimal, especially when you learned about typical MVP patterns somewhere.
Things like instance and controller mean different things there.
My proposal would be the following:
resource
stays the sameinstance
gets renamed topager
controller
altogether, this can be justresource
(it would reflect the relationship to resource better anyway)Here's an example of how the
resource
would look like:Let me know what you think!
The text was updated successfully, but these errors were encountered: