Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixed passing of command arguments that are of non-primitive type #804

Merged
merged 3 commits into from
Jul 3, 2020

Conversation

exyi
Copy link
Member

@exyi exyi commented Jan 26, 2020

The command arguments must be deserialized with knowledge of the expected type.

Apart from that, I also had to fix strange behavior of KnockoutHelper.GeneratePostbackExpression

The command arguments must be deserialized with knowledge of the expected type.

Apart from that, I also had to fix strange behavior of KnockoutHelper.GeneratePostbackExpression
@tomasherceg tomasherceg self-requested a review June 5, 2020 11:51
@tomasherceg tomasherceg added this to the Version 2.5 milestone Jun 12, 2020
… (it doesn't work when there is an input[type=text] in the page)
@@ -22,7 +22,7 @@ public void Feature_CommandArguments_CommandArguments()
var text = browser.Single("[data-ui='value']");
AssertUI.InnerTextEquals(text, "Nothing here");

browser.Single("[data-ui='button'] button").Click();
browser.Single("[data-ui='button1'] button").Click().Wait();
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I can't see any reason for using Wait() method here. Please use WaitFor().

@tomasherceg tomasherceg merged commit 028e864 into master Jul 3, 2020
@tomasherceg tomasherceg deleted the fix-object-command-args branch July 3, 2020 11:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants