[🚀 Feature]: [dotnet] [bidi] Introduce CancellationToken for async commands #16989
Description
Description
Now:
await context.NavigateAsync("https://google.com/", new() { Wait = ReadinessState.Complete, Timeout = TimeSpan.FromSeconds(50) });
// 30 secs by defaultProposed:
await context.NavigateAsync("https://google.com/", new() { Wait = ReadinessState.Complete, Timeout = TimeSpan.FromSeconds(50) }, CancellationToken.None); // any optional tokenAPI:
ExecuteSomeCommandAsync(string param1, ..., ExecuteSomeCommandOptions? = null, CancellationToken? cancellationToken = default)Implementation notes
It should honor both provided, Timeout + CancellationToken via linked cancellation token source.
Have you considered any alternatives or workarounds?
Timeout is a winner in 99% cases. But to be modern library just follow best practices.