[🚀 Feature]: [dotnet] [bidi] Don't throw exception when CallFunction/Evaluate in Script module

[nvborisenko]

Feature and motivation

await context.Script.CallFunctionAsync("() => { return ['hi']; }", false);

It throws an .Net exception rather than returning EvaluateResult BiDi object.

script.EvaluateResult = (
  script.EvaluateResultSuccess /
  script.EvaluateResultException
)

Now, .Net methods throw if the result is EvaluateResultException. It is not ideal, low-level binding should not introduce additional logic on top of specification.

Why:

• We are hiding all data included into EvaluateResultException, trying to include it in .Net Exception type.
• If in future new derived type will be introduced in the spec (like "PartiallySuccess"), then we will be in **s (problematic situation)

Usage example

Before:

public Task<EvaluateResult.Success> CallFunctionAsync(...)

After:

public Task<EvaluateResult> CallFunctionAsync(...)

NOTE: Keeping in mind implicit/explicit type conversions in .NET.

[github-actions]

@nvborisenko, thank you for creating this issue. We will troubleshoot it as soon as we can.

---

Info for maintainers

Triage this issue by using labels.

If information is missing, add a helpful comment and then I-issue-template label.

If the issue is a question, add the I-question label.

If the issue is valid but there is no time to troubleshoot it, consider adding the help wanted label.

If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C), add the applicable G-* label, and it will provide the correct link and auto-close the issue.

After troubleshooting the issue, please add the R-awaiting answer label.

Thank you!

[github-actions]

This issue has been automatically locked since there has not been any recent activity since it was closed. Please open a new issue for related bugs.