refactor: unify locator factories naming and toString implementations#1538
Conversation
bcac648 to
8e7d772
Compare
|
I'm not quite sure I want to lend this change. It would only create more hassle for end users without giving any actual benefits |
|
@mykola-mokhnach ok, that's up to you, feel free to close the PR |
|
@SrinivasanTarget What do you think regarding the above? |
|
We could do it this way - old locators stay, but get |
|
I was also thinking about renaming MobileBy to AppiumBy. MobileBy makes sense for iOS and Android, but does not make sense for mac and windows and also other non-mobile drivers, so we need some more generic name. The renaming strategy could be exactly the same as described above |
|
I like the idea to add Deprecate tag and also rename to AppiumBy |
AppiumBy seems more relevant and as you said let's deprecate complete MobileBy stuffs. |
8e7d772 to
2cf96a7
Compare
MobileBy methods naming and toString implementationstoString implementations
2cf96a7 to
ba527a7
Compare
ba527a7 to
c429c4e
Compare
| } | ||
|
|
||
| @Override public String toString() { | ||
| return String.format("By.%s: %s", locatorName, remoteParameters.value()); |
c429c4e to
667f81a
Compare
Change list
Keep the unified naming of methods and
toStringimplementations.Types of changes
What types of changes are you proposing/introducing to Java client?
Put an
xin the boxes that applyDetails
Unify locator factory-methods naming and
toStringimplementations to follow the same approach as it's done in Selenium.