Merge lp:~akretion-team/openerp-fiscal-rules/7.0-fix-on-change-yaml-importer-parsing into lp:openerp-fiscal-rules

[Raphaël Valyi - http://www.akretion.com]

[FIX] removed on_change formatting in XML views as it would make the yaml import parser fail to parse the on_change definitions

[Pedro Manuel Baeza (pedro.baeza)]

Strange behaviour...

review: Approve (code review)

[Raphaël Valyi - http://www.akretion.com (rvalyi)]

BTW, this is the kind of YAML parser error you get if you let these linebreaks in the views:

https://travis-ci.org/openerpbrasil/l10n_br_core/builds/15968791#L1035

It's more an issue in OpenERP server probably, but as fixing anything in the server takes years, I propose simply removing the linebreaks as in this MP.

[Yannick Vaucher @ Camptocamp (yvaucher-c2c)]

LGTM

review: Approve (code review, no tests)

=== modified file 'account_fiscal_position_rule_sale/sale_view.xml'
--- account_fiscal_position_rule_sale/sale_view.xml	2013-02-11 13:36:48 +0000
+++ account_fiscal_position_rule_sale/sale_view.xml	2013-12-25 19:17:37 +0000
@@ -9,27 +9,17 @@
                <field name="priority">26</field>
                <field name="arch" type="xml">
                 <field name="shop_id" position="attributes">
-                    <attribute name="on_change">
-                        onchange_shop_id(shop_id, context, partner_id, partner_invoice_id, partner_shipping_id)
-                    </attribute>
+                    <attribute name="on_change">onchange_shop_id(shop_id, context, partner_id, partner_invoice_id, partner_shipping_id)</attribute>
                 </field>
                 <field name="partner_invoice_id" position="attributes">
-                    <attribute name="on_change">
-                        onchange_address_id(partner_invoice_id, partner_shipping_id, partner_id, shop_id, context)
-                    </attribute>
+                    <attribute name="on_change">onchange_address_id(partner_invoice_id, partner_shipping_id, partner_id, shop_id, context)</attribute>
                 </field>
                 <field name="partner_shipping_id" position="attributes">
-                    <attribute name="on_change">
-                        onchange_address_id(partner_invoice_id, partner_shipping_id, partner_id, shop_id, context)
-                    </attribute>
+                    <attribute name="on_change">onchange_address_id(partner_invoice_id, partner_shipping_id, partner_id, shop_id, context)</attribute>
                 </field>
                 <field name="partner_id" position="attributes">
-                    <attribute name="on_change">
-                        onchange_partner_id(partner_id, context)
-                    </attribute>
-                    <attribute name="context">
-                        {'shop_id': shop_id}
-                    </attribute>
+                    <attribute name="on_change">onchange_partner_id(partner_id, context)</attribute>
+                    <attribute name="context">{'shop_id': shop_id}</attribute>
                 </field>
             </field>
         </record>