summaryrefslogtreecommitdiff
path: root/addons/analytic_user_function/analytic_user_function_view.xml
diff options
context:
space:
mode:
authorXavier Morel <xmo@openerp.com>2013-06-24 07:59:29 +0200
committerXavier Morel <xmo@openerp.com>2013-06-24 07:59:29 +0200
commit11a0ece5438d551963b5c9cdbb95720b0e91d98d (patch)
tree5eaead53f66ace0df368eee27414ee7f5d6911ae /addons/analytic_user_function/analytic_user_function_view.xml
parente2c795e29764c1b65b3cf34ce3120e17a0fe399f (diff)
[FIX] evaluation context structures not being round-tripped through eval
JS objects are converted to py.object when passed in through the evaluation context. py.object are not serializable by default (because that doesn't really make sense), which breaks when the input is intended as a dict and returned (e.g. o2m values, which are triples of (int, int?, dict?)). Intuitively, JS objects passed as part of the context should be mostly JSON-ish and thus dicts, but that turns out not work work as some addons use attribute accesses within contexts (e.g. parent.access in account/account_invoice_view.xml) => Temporarily solve by converting raw js objects to an "attributed dict" which acts as both a dict and an object and can be converted to JSON. Ideally, py.js should provide for a pluggable conversion, or should use an attributed mapping internally. See issues 21 and 23. lp bug: https://launchpad.net/bugs/1182101 fixed bzr revid: xmo@openerp.com-20130624055929-3rtkgqrp4o87pvau
Diffstat (limited to 'addons/analytic_user_function/analytic_user_function_view.xml')
0 files changed, 0 insertions, 0 deletions