Replies: 1 comment
-
Given that Microsoft's own code throws the ArgumentNullException where appropriate, I'd imagine that just validating the parameters with either a String.Contains or Regex.IsMatch would be a reasonable implementation. In principle, that would probably be similar to the logic that would satisfy this design warning here |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I have a static method on a ReadOnlyList that takes a string as a parameter. The search string accepts a full name, email address, transaction number, a transaction number range, a single date and a date range. What is the best way to protect the parameter from unexpected characters?
Beta Was this translation helpful? Give feedback.
All reactions