[diag] Don't check for RNG ambiguities on management rules
authorSylvain Thénault <sylvain.thenault@logilab.fr>
Wed, 06 Dec 2017 16:17:28 +0100
changeset 2891 38f882d0cee5
parent 2890 e1fd97e85af2
child 2892 2cc69ec08306
[diag] Don't check for RNG ambiguities on management rules I don't think we care about such rules'order and they should usually be fixed in the profile, so don't check them. If one wish to check them at some point, it should add ordering on relevant entities and extend consistently the xsd2yams.MULTIPLE_CHILDREN list.
cubicweb_seda/entities/diag.py
--- a/cubicweb_seda/entities/diag.py	Wed Dec 06 16:15:04 2017 +0100
+++ b/cubicweb_seda/entities/diag.py	Wed Dec 06 16:17:28 2017 +0100
@@ -269,7 +269,8 @@
     'seda_keyword': 'seda_indexation_tab',
     'seda_physical_data_object': 'seda_data_objects_tab',
     'seda_recipient_from': 'seda_agents_tab',
-    'seda_ref_non_rule_id_from': 'seda_management_tab',
+    # don't care about order on this one, for now at least
+    # 'seda_ref_non_rule_id_from': 'seda_management_tab',
     'seda_references': 'seda_relations_tab',
     'seda_related_transfer_reference': 'seda_at_related_transfers_tab',
     'seda_relationship': 'seda_do_relations',