Keep-alive message causes an exception

[BruceCarson]

I'm using a websocket service that uses a single newline character "\n" as a keep-alive message. However on send, Websocket.Client throws an exception. I receive the keep-alives FROM the server (also "\n") with no issues.

Is there any problem with changing the ValidateInput(string value, string name) to using:
string.IsNullOrEmpty(value)
instead of:
string.IsNullOrWhitespace(value)

If there is no problem, could you change in the next version?

[Marfusios]

Hello @BruceCarson ,

seems fine to me, could you provide PR with the change?

[BruceCarson]

One of your tests is failing - even without changing code: OnClose_ShouldWorkCorrectly. I get:
Assert.Equal() Expected: Aborted Actual: Closed
Seems like this test is out-of-date?
I'll change to expecting Closed in the pull request - but it has nothing to do with my change ;)

[BruceCarson]

Done.

[Marfusios]

Hmm, that's weird, hopefully, it is not a breaking change in a .NET Core

[BruceCarson]

Update:
I worked around the issue by doing this:
var bytes = Encoding.UTF8.GetBytes("\n");
Client.Send(bytes);
But also submitted a pull request to allow using just: Client.Send("\n");