Handle create=false when exact matching

When a facility list item is submitted with create=false and there is
no match found, a FacilityListItem is created with facility_id=None.
When another facility list item is submitted which exact matches that
FacilityListItem, an error was being thrown. Instead, we now filter
out FacilityListItems where the facility_id=None, allowing us to match
to the next best option (if one exists) or pass the FacilityListItem
on to the dedupe process.

src/django/api/matching.py

@@ -116,7 +116,8 @@ def exact_match_items(messy, contributor):
 
     matched_items = FacilityListItem.objects \
         .filter(status__in=[FacilityListItem.MATCHED,
-                            FacilityListItem.CONFIRMED_MATCH])
+                            FacilityListItem.CONFIRMED_MATCH]) \
+        .exclude(facility_id=None)
     active_item_ids = FacilityMatch.objects \
         .filter(status__in=[FacilityMatch.AUTOMATIC,
                             FacilityMatch.CONFIRMED,

src/django/api/tests.py

@@ -6026,6 +6026,14 @@ def test_creates_nonstandard_fields(self):
         self.assertEquals(1, len(fields))
         self.assertIn('extra_1', fields)
 
+    def test_exact_matches_with_create_false(self):
+        self.join_group_and_login()
+        url_with_query = '{}?create=false&public=true'.format(self.url)
+        response = self.client.post(url_with_query, self.valid_facility)
+        self.assertEqual(response.status_code, 200)
+        response_two = self.client.post(url_with_query, self.valid_facility)
+        self.assertEqual(response_two.status_code, 200)
+
 
 class FacilityCreateBodySerializerTest(TestCase):
     def test_valid_data(self):