chore(spp_import_match): apply CI formatter + regenerate README (#991)

Author: emjay0921

spp_import_match/README.rst

@@ -393,6 +393,26 @@ Test 12: Security — Non-Admin Access
 Changelog
 =========
 
+19.0.2.0.2
+~~~~~~~~~~
+
+- chore(views): hide the conditional-gate columns (``Is Conditional``,
+  ``Condition Field``, ``Condition Value``) from the match-rule fields
+  list — the schema and matching-engine wiring stay in place, but no
+  current import flow uses the gate, so the columns are kept out of the
+  UI until a real use case lands.
+
+19.0.2.0.1
+~~~~~~~~~~
+
+- fix(matching): add a ``condition_field_id`` Many2one column to
+  ``spp.import.match.fields`` and rewrite the matching loop so
+  conditional rows act as pure gates — never added to the DB search
+  domain. Renames the IMPORTED VALUE column heading to **Condition
+  Value**. Fixes the case where a CSV-only metadata column (e.g.
+  ``data_source``) was being injected into the search domain and causing
+  zero matches.
+
 19.0.2.0.0
 ~~~~~~~~~~
 

spp_import_match/models/import_match.py

@@ -77,11 +77,7 @@ def _match_find(self, model, converted_row, imported_row):
                     # to the DB search domain — the gate column may be a
                     # CSV-only metadata field (e.g. `data_source`) that
                     # doesn't exist on the registrant model.
-                    gate_field_name = (
-                        field.condition_field_id.name
-                        if field.condition_field_id
-                        else field.field_id.name
-                    )
+                    gate_field_name = field.condition_field_id.name if field.condition_field_id else field.field_id.name
                     if imported_row.get(gate_field_name) != field.imported_value:
                         combination_valid = False
                         break

spp_import_match/static/description/index.html

@@ -804,6 +804,28 @@ <h2><a class="toc-backref" href="#toc-entry-15">Changelog</a></h2>
 </div>
 </div>
 <div class="section" id="section-1">
+<h1>19.0.2.0.2</h1>
+<ul class="simple">
+<li>chore(views): hide the conditional-gate columns (<tt class="docutils literal">Is Conditional</tt>,
+<tt class="docutils literal">Condition Field</tt>, <tt class="docutils literal">Condition Value</tt>) from the match-rule fields
+list — the schema and matching-engine wiring stay in place, but no
+current import flow uses the gate, so the columns are kept out of the
+UI until a real use case lands.</li>
+</ul>
+</div>
+<div class="section" id="section-2">
+<h1>19.0.2.0.1</h1>
+<ul class="simple">
+<li>fix(matching): add a <tt class="docutils literal">condition_field_id</tt> Many2one column to
+<tt class="docutils literal">spp.import.match.fields</tt> and rewrite the matching loop so
+conditional rows act as pure gates — never added to the DB search
+domain. Renames the IMPORTED VALUE column heading to <strong>Condition
+Value</strong>. Fixes the case where a CSV-only metadata column (e.g.
+<tt class="docutils literal">data_source</tt>) was being injected into the search domain and causing
+zero matches.</li>
+</ul>
+</div>
+<div class="section" id="section-3">
 <h1>19.0.2.0.0</h1>
 <ul class="simple">
 <li>Initial migration to OpenSPP2</li>

spp_import_match/tests/test_import_match_model.py

@@ -130,9 +130,7 @@ def test_match_find_conditional_match(self):
         provide the actual search predicate. Here `name` is the gate and
         `email` is the search predicate.
         """
-        partner = self.env["res.partner"].create(
-            {"name": "ConditionalMatchTest", "email": "conditional@example.com"}
-        )
+        partner = self.env["res.partner"].create({"name": "ConditionalMatchTest", "email": "conditional@example.com"})
         match = self._create_match_rule(
             [
                 {