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

Move Pager to azure_core since it's Azure-specific #1909

Open
heaths opened this issue Nov 12, 2024 · 2 comments
Open

Move Pager to azure_core since it's Azure-specific #1909

heaths opened this issue Nov 12, 2024 · 2 comments
Labels
Azure.Core The azure_core crate Client This issue points to a problem in the data-plane of the library.

Comments

@heaths
Copy link
Member

heaths commented Nov 12, 2024

As came up during a REST API LT meeting, paging is Azure-specific and the Pager<T> should be moved back into azure_core. Will have to see how that impacts the overall response model i.e., does it try to create any pager when deserializing? I'm pretty sure not, but use it as an example of things to check. /cc @jhendrixMSFT @JeffreyRichter

@heaths heaths added Azure.Core The azure_core crate Client This issue points to a problem in the data-plane of the library. labels Nov 12, 2024
@heaths heaths changed the title Move to since it's Azure-specific Move Pager to azure_core since it's Azure-specific Nov 12, 2024
@JeffreyRichter
Copy link
Member

Yes, paging & LROs is Azure-specific.

@heaths
Copy link
Member Author

heaths commented Nov 12, 2024

I knew LROs were. Those are still in azure_core. I'll just need to move paging...if I can (pretty sure I can).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Azure.Core The azure_core crate Client This issue points to a problem in the data-plane of the library.
Projects
None yet
Development

No branches or pull requests

2 participants