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
The wait* methods take optional interval and timeout values, and fall back to hard coded defaults if not set.
I would like for the defaults to be configurable.
It's straightforward to wrap the methods, so this is certainly not critical, but I think it would be nice
Suggested implementation:
Add a setDefaultWaitOptions method that can update the options that the wait* methods fall back to
Describe alternatives you've considered:
There could be a way to read from a config file on environment.
Maybe it would be better to have separate methods for setting them.
If desired, a stack could be implemented to push/pop settings for regions to have different defaults.
I really don't think it needs to be this complicated though
Describe the feature you'd like:
The wait* methods take optional
interval
andtimeout
values, and fall back to hard coded defaults if not set.I would like for the defaults to be configurable.
It's straightforward to wrap the methods, so this is certainly not critical, but I think it would be nice
Suggested implementation:
Add a
setDefaultWaitOptions
method that can update the options that thewait*
methods fall back toDescribe alternatives you've considered:
There could be a way to read from a config file on environment.
Maybe it would be better to have separate methods for setting them.
If desired, a stack could be implemented to push/pop settings for regions to have different defaults.
I really don't think it needs to be this complicated though
Teachability, Documentation, Adoption, Migration Strategy:
Users would be able to call the function in a setup file and then use the
wait*
functions normally, but with updated settingsThe text was updated successfully, but these errors were encountered: