You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To prevent naming conflicts it could be great if page object implementations for page object interfaces defined inside a class would also be created as static inner classes .
for example:
PageObjectClass.InnerPageObjectInterface would be created as PageObjectClassImpl.InnerPageObjectInterfaceImpl
This usually shouldn't affect users of the framework. There's just one exception if Implementation Classnames are used explicitely in default methods of PageObject
The text was updated successfully, but these errors were encountered:
To prevent naming conflicts it could be great if page object implementations for page object interfaces defined inside a class would also be created as static inner classes .
for example:
PageObjectClass.InnerPageObjectInterface would be created as PageObjectClassImpl.InnerPageObjectInterfaceImpl
This usually shouldn't affect users of the framework. There's just one exception if Implementation Classnames are used explicitely in default methods of PageObject
The text was updated successfully, but these errors were encountered: