Skip to content
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

Propagate resolved value of 'renderQuery' promise through 'refresh' #1315

Merged
merged 2 commits into from
Jan 9, 2020

Conversation

msssk
Copy link
Contributor

@msssk msssk commented Oct 5, 2016

The renderQuery method returns a promise that resolves to an array of the rendered row elements. It appears to be an oversight that this value is discarded by the refresh method.

The `renderQuery` method returns a promise that resolves to an array of the rendered row elements. It appears to be an oversight that this value is discarded by the `refresh` method.
@kfranqueiro
Copy link
Member

IIUC, Pagination#refresh currently returns results, not rows, so this would be somewhat inconsistent. I think it should be possible to return results rather than rows here too though, so would that be a better idea?

@edhager edhager removed their assignment Nov 1, 2017
…ination

Add refresh result tests for OnDemandList and Pagination
@msssk msssk merged commit 11bf1f2 into master Jan 9, 2020
@msssk msssk deleted the refresh-results branch January 9, 2020 04:03
msssk added a commit that referenced this pull request Apr 18, 2020
…ws (#1315)

`Pagination#refresh()` returns a promise that resolves to the `QueryResults` object for the rendered rows.

This PR updates `OnDemandList#refresh()` to do the same, which seems to have been an oversight. Tests are also added to verify this behavior.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants