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
At the moment, the @WithTimeout annotation can only be applied to fields.
Often when working with widgets, having the root element ready means that the inner elements will also be ready for interaction.
@WithTimeout annotation is great for reducing the time spent searching for inner elements, but requires application for each field.
It would be nice to have the ability to apply annotations to all widget class fields at once.
Reactions are currently unavailable
Activity
ghost changed the title [-]FR: Make @WithTimeout applicable to widgets[/-][+]FR: Make @WithTimeout applicable to classes[/+]on Sep 19, 2024
@mykola-mokhnach Is this something I can help look into? Does it align with the project to implement something like this? I have not looked into it, but I want to understand if this is feasible or the Appium team thinks it's good to have this feature.
I personally don't really support the idea of page objects. They contain lots of implicit logic, and often are sources of unexpected behaviours. Widgets were build on top of that, which made the overall implementation even more complex and fragile. Also, the feature request itself does not seem to have high traction.
Nevertheless feel free to work on it if the implementation is not going to be breaking.
Activity
[-]FR: Make @WithTimeout applicable to widgets[/-][+]FR: Make @WithTimeout applicable to classes[/+]pujagani commentedon Jul 7, 2025
@mykola-mokhnach Is this something I can help look into? Does it align with the project to implement something like this? I have not looked into it, but I want to understand if this is feasible or the Appium team thinks it's good to have this feature.
mykola-mokhnach commentedon Jul 7, 2025
I personally don't really support the idea of page objects. They contain lots of implicit logic, and often are sources of unexpected behaviours. Widgets were build on top of that, which made the overall implementation even more complex and fragile. Also, the feature request itself does not seem to have high traction.
Nevertheless feel free to work on it if the implementation is not going to be breaking.
pujagani commentedon Jul 8, 2025
Thank you so much. That gives me a better context. Will try and pick something else that can help the project better.