Is it intentional that NullOrEmpty and NullOrWhiteSpace are ignoring the custom message when doing a Null Check?

[Miljankg]

Hello again :)

While working on #168, I noticed that NullOrEmpty and NullOrWhiteSpace are not passing the custom message to the Null check and only use it for the empty/white-space check.

While thinking if this is an issue, I thought that there may be a use case where the custom message is usually only applicable to the empty/white-space check.

However, when I tried to use the API, I was normally setting the custom message so that it covers both cases. E.g.:
Guard.Against.NullOrWhiteSpace(something, "something", "Null, empty or white space are prohibited.");.
The final error message would look like this:
Null, empty, or white space are prohibited. (Parameter 'something')

Is the current implementation intentional or should it be improved?

Thanks in advance.

[Miljankg]

Answered as a part of the #169. A new issue will be created.

[Miljankg]

Issue created: #174