Skip to content

Conversation

JohnVillalovos
Copy link
Member

If a caller calls a list() method with both iterator=True (or as_list=False) and page=X then emit a UserWarning as the options are mutually exclusive.

@JohnVillalovos JohnVillalovos requested a review from nejch January 25, 2023 22:50
@JohnVillalovos JohnVillalovos force-pushed the jlvillal/warn_incompatible branch from 8aed6c8 to 7159747 Compare January 25, 2023 22:50
@JohnVillalovos JohnVillalovos changed the title chore: add a UserWarning if use both iteratore=True and page=X chore: add a UserWarning if use both iterator=True and page=X Jan 25, 2023
@nejch nejch changed the title chore: add a UserWarning if use both iterator=True and page=X chore: add a UserWarning if both iterator=True and page=X are used Jan 26, 2023
Copy link
Member

@nejch nejch left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @JohnVillalovos just a little typo there!

Hopefully we can remove as_list for a major bump at some point and simplify these checks 😁

If a caller calls a `list()` method with both `iterator=True` (or
`as_list=False`) and `page=X` then emit a `UserWarning` as the options
are mutually exclusive.
@JohnVillalovos JohnVillalovos force-pushed the jlvillal/warn_incompatible branch from 7159747 to bec4f6a Compare January 26, 2023 15:14
@nejch nejch merged commit 8e85791 into main Jan 26, 2023
@nejch nejch deleted the jlvillal/warn_incompatible branch January 26, 2023 16:11
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.

2 participants