Fix StringChecker Softlock bug #263
                
     Draft
            
            
          
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
Fix StringChecker bugs
- I confirm this PR is at its final form and will not receive more pushes to it unless modifications are required.
- I confirm this PR has been previously tested by me and has no apparent issues.
- I confirm this PR is complying with this project's Contribution Guidelines.
- I confirm this PR is complying with this project's Syntax Ruleset.
This PR fixes a possible softlock state that could be caused by the user submitting
IllegalChar's, the Checker function can slip whitespaces due to using string.Contains improperlyPR also removes a superfluous call to string.IsNullOrEmpty, string.IsNullOrWhitespace already checks against string.Empty as can be seen in it's XML summary explicitly stated.