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

An attempt to add paging support in a generic way. #147

Merged
merged 1 commit into from
May 28, 2024
Merged

Conversation

mivano
Copy link
Owner

@mivano mivano commented May 22, 2024

No description provided.

@DanielSpindler83
Copy link
Contributor

I did some testing on this branch and it works for calls I make that need more pages and no known impact to calls for single pages.
Looks good to go.

@mivano
Copy link
Owner Author

mivano commented May 25, 2024

Thanks for validating. By the way, I did not want to overrule your PR, as you also took the time to come up with an implementation. So I hope you are okay with this approach as well?

@mivano mivano marked this pull request as ready for review May 25, 2024 21:40
@DanielSpindler83
Copy link
Contributor

100% ok with this approach. It is nice and clean. I am enjoying the learning and engagement. Thanks for checking.

@MvRoo
Copy link
Contributor

MvRoo commented May 28, 2024

I have been testing costByResource, which didn't support paging before, and it is looking fine until now. Have exported > 38k lines on one occasion.

@mivano
Copy link
Owner Author

mivano commented May 28, 2024

Thanks for validating this change guys! I will merge it and prepare a package.

@mivano mivano merged commit 1eb9d89 into main May 28, 2024
3 checks passed
@mivano mivano deleted the feat/nextlink branch May 28, 2024 19:42
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