Closed kelmelzer closed 20 hours ago
@kelmelzer, thank you for your contribution. In order for the build to pass, you will need to update the selenium dependencies as part of this PR.
@kelmelzer, thank you for your contribution. In order for the build to pass, you will need to update the selenium dependencies as part of this PR.
Sure thing. I did that by hand but will fork it and actually build it on my personal machine shortly :)
@kelmelzer, thank you for your contribution. In order for the build to pass, you will need to update the selenium dependencies as part of this PR.
Sure thing. I did that by hand but will fork it and actually build it on my personal machine shortly :)
This will not work for you because the Selenium team needs to fix the encapsulation they broke on internal Response Execute
.
So it would be best if you waited for the next release.
Closing pull request. I made a new one which fixes the build and wraps ExecuteAsync() properly
I think this should fix it in Selenium 4.22+, but its untested so far of course. :)
List of changes
Implemented ICommandExecutor's ExecuteAsync(). Moved Execute() code to there and call it from Execute() with Task.Run()
Types of changes
What types of changes are you proposing/introducing to the .NET client? Put an
x
in the boxes that applyDocumentation
This can be done by navigating to the documentation section on http://appium.io selecting the appropriate command/endpoint and clicking the 'Edit this doc' link to update the C# example
Integration tests