LHC: Limiting overtriggering (#4462)

* HasLHC: Adding failing tests for improper trigger type * LHC: We want start to limit overtriggering and only if there isn't other information in the query
duckduckgo · Aug 28, 2017 · a46679a · a46679a
1 parent 9b128b8
commit a46679a
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/lib/DDG/Goodie/HasLHCDestroyedWorld.pm b/lib/DDG/Goodie/HasLHCDestroyedWorld.pm
@@ -8,14 +8,14 @@ use strict;
 zci answer_type => 'has_lhcdestroyed_world';
 zci is_cached => 1;
 
-triggers any => 'has the large hadron collider destroyed the world',
+triggers start => 'has the large hadron collider destroyed the world',
                 'has the lhc destroyed the world',
                 'has the large hadron collider destroyed the earth',
                 'has the lhc destroyed the earth';
 
 # Handle statement
 handle remainder => sub {
-
+    return unless /^(yet)?$/;
     return "Nope.",
         structured_answer => {
             id => 'has_lhcdestroyed_world',

diff --git a/t/HasLHCDestroyedWorld.t b/t/HasLHCDestroyedWorld.t
@@ -40,7 +40,7 @@ ddg_goodie_test(
     'has the lhc destroyed the earth yet'                   => test_zci(@no),
     'has the lhc destroyed the earth'                       => test_zci(@no),
 
-
+    'in science fiction has the large hadron collider destroyed the world' => undef,
     'large hadron collider'                                 => undef,
     'could the large hadron collider destroyed the world'   => undef,
     'will the large hadron collider destroy the earth'      => undef