Expression Guard about guardclauses HOT 9 CLOSED

yes, if someone wants to implement support for it, I'd look at the PR. Just reference this issue number in the description. Thanks, @wgnf

from guardclauses.

Hmm... yeah, that's fair. I think maybe I missed it due to its naming. Ok, let's just say this is done, then. 😃

from guardclauses.

This is nice. Any reason you want to limit this only for "struct"?

from guardclauses.

Be aware that this can lead to performance issues if abused.

safakgur/guard#13

from guardclauses.

Let's implement this and see if there are any issues.

from guardclauses.

If someone wants to deal with string properties with custom validations, this will not allow. Otherwise, I've added the required tests. Let me know. @ardalis

from guardclauses.

@ardalis do you still want this to be implemented? if so, i'd love to have a go at this :)

from guardclauses.

Just scrolling through code to see how things are done i stumbled upon this one:

https://github.com/ardalis/GuardClauses/blob/main/src/GuardClauses/GuardClauseExtensions.cs#L581-L589

Guard.Against.InvalidInput seems to already be the "Expression Guard" that you want to implement in this issue 🤔

from guardclauses.

The only thing that is different here is that you mention a IGuardClause<T> with a Value in that (new) interface, which I'm unable to find.

Or is that the new feature you wanted to implement and I just didn't get the hint? :D @ardalis

from guardclauses.