[py] Type WebElement.get_attribute name - #18028
Conversation
Qodo reviews are paused for this user.Troubleshooting steps vary by plan Learn more → On a Teams plan? Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center? |
|
@adamtheturtle can you check the PR description? Looks like the formar went wrong. Also, can you please follow the PR template? |
|
Thanks — I fixed the formatting and rewrote the description using the current PR template, including the AI-assistance disclosure. |
Code Review by Qodo🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)
Great, no issues found!Qodo reviewed your code and found no material issues that require reviewTip of the day💡 Did you know, you can add REVIEW.md to your repo root and Qodo follows it on every PR |
diemol
left a comment
There was a problem hiding this comment.
While this is correct, I don't understand why only adding a type to this method when there are other two that also need this. Ideally we want to have the whole file typed where it applies, and not these one off PRs. I hope that makes sense.
|
@diemol I do not have capacity to expand the scope of this. |
Extends this PR's get_attribute annotation to the two sibling methods that share the same untyped name parameter, as requested in review. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
|
Code review by qodo was updated up to the latest commit 58f2a72 |
🔗 Related Issues
None.
💥 What does this PR do?
Annotates the attribute or property name accepted by
WebElement.get_attributeasstr, so strict Pyright consumers no longer see a partially unknown bound method type.🔧 Implementation Notes
The return type remains
str | None; this PR only adds the missing parameter annotation.Validation:
git diff --checkpassed.(name: str) -> str | None.🤖 AI assistance
💡 Additional Considerations
This is annotation-only and does not change runtime behavior.
🔄 Types of changes