Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently with the
w-table
pagination if you adjust thepagination.page
value a watcher is fired off to re-calculate the pagination values so they're adjusted correctly.The method that gets called to update everything is
updatePaginationConfig
, which you can pass an object of data to for internal uses adjusting the page and total it would seem?There's a section of this code that assigns some variables for shorthand use with some math, but they override the parameter variables. So then this logic
if (page) this.goToPage(page)
is always true because we've overridden thepage
variable, so it will attempt to re-load the page again. This causes my setup to loop infinitely, unless it hits 0. Perhaps I'm using this wrong though?Currently the way I'm attempting to use it like this:
And for fetching I'm using:
This causes some really weird behavior unless we use the fix I have in this PR. Again, perhaps I'm doing something wonky here. I'm fine if you toss this out. I can always use the slot for what I need.