-
Notifications
You must be signed in to change notification settings - Fork 564
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
feat: add AppiumBy instead of MobileBy #659
Conversation
from selenium.webdriver.common.by import By | ||
|
||
|
||
class AppiumBy(By): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd prefer it to not be a breaking change. E.g. keep the MobileBy strategy, but simply mark it as deprecated
AppiumBy may then be inherited from MobileBy to avoid unnecessary duplication.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
MobileBy.ID
in appium/webdriver/common/mobileby.py (inherits AppiumBy) etc are str
. AppiumBy.ID
also str
. So basically both ID are set as id
to find_element, for example.
I think they do not have breaking change... something wrong?
Yea, I was finding the way to print deprecation message when MobileBy.ID
was called or when MobileBy.ID
was given in find_element. But it was simply str
.
So currently I've put the deprecation message in the module description.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe we could use https://www.py4u.net/discuss/182959 (https://pypi.org/project/deprecation/#description) to mark things as deprecated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
mm, the deprecation package also does not work for str of class variables?
Yea, I think only documentation can mention it.
mm, it looks like current building docs partially depend on the published python client module. |
part of #645