-
Notifications
You must be signed in to change notification settings - Fork 436
Wrong type annotation in workbook.refresh #1318
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
Comments
pes-magic
added a commit
to pes-magic/server-client-python
that referenced
this issue
Nov 13, 2023
`workbook.refresh` is implemented to accept both `WorkbookItem` and `str` as arguments, but the type annotation describes it as receiving `str`, which can cause false warnings in static analysis. Since the documentation states that it receives `workbook_item`, the name of the argument is also changed from `workbook_id` to `workbook_item`. Issue: tableau#1318
@pes-magic Can you mark this as closed by #1319? |
Sure, thank you for reminding me |
gconklin
pushed a commit
to gconklin/tableauserverclient
that referenced
this issue
May 28, 2024
`workbook.refresh` is implemented to accept both `WorkbookItem` and `str` as arguments, but the type annotation describes it as receiving `str`, which can cause false warnings in static analysis. Since the documentation states that it receives `workbook_item`, the name of the argument is also changed from `workbook_id` to `workbook_item`. Issue: tableau#1318
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
workbooks.refresh
is implemented to receiveworkbook_id
as a string type argument, but it can actually receiveWorkbookItem
as well. The documentation also states that it receivesworkbook_item
.Implementation: https://github.com/tableau/server-client-python/blob/master/tableauserverclient/server/endpoint/workbooks_endpoint.py#L91
Documentation: https://tableau.github.io/server-client-python/docs/api-ref#workbooksrefresh
Versions
To Reproduce
Nothing to do
Results
Static code analysis displays false warnings
The text was updated successfully, but these errors were encountered: