From 6cbc8687de5b660f34ba5fcb045f9154f8088d88 Mon Sep 17 00:00:00 2001
From: Mark McDowall <markus.mcd5@gmail.com>
Date: Wed, 15 Jan 2014 16:22:22 -0800
Subject: [PATCH] Better way to fix empty string split results

---
 .../Specifications/NotRestrictedReleaseSpecification.cs       | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

diff --git a/src/NzbDrone.Core/DecisionEngine/Specifications/NotRestrictedReleaseSpecification.cs b/src/NzbDrone.Core/DecisionEngine/Specifications/NotRestrictedReleaseSpecification.cs
index 8cfe45cf3..7ba369944 100644
--- a/src/NzbDrone.Core/DecisionEngine/Specifications/NotRestrictedReleaseSpecification.cs
+++ b/src/NzbDrone.Core/DecisionEngine/Specifications/NotRestrictedReleaseSpecification.cs
@@ -37,12 +37,10 @@ namespace NzbDrone.Core.DecisionEngine.Specifications
                 return true;
             }
 
-            var restrictions = restrictionsString.Split('\n');
+            var restrictions = restrictionsString.Split(new []{ '\n' }, StringSplitOptions.RemoveEmptyEntries);
 
             foreach (var restriction in restrictions)
             {
-                if (String.IsNullOrWhiteSpace(restriction)) continue;
-
                 if (subject.Release.Title.ToLowerInvariant().Contains(restriction.ToLowerInvariant()))
                 {
                     _logger.Trace("{0} is restricted: {1}", subject, restriction);