b87102f22e
Custom keys from user context may be used in action contexts (not just e.g. searchview filters). For instance, have a custom key context_salesteam (in the user model) and an action defining some search default as a function of the salesteam. In that case, the action's context evaluation (view.js:~275) will blow up. Ensure that does not happen. Note: eval_contexts already injects user_context in the reduction of contexts to evaluate. It should be possible to alter the reduction function to avoid having to inject instance.session.user_context through pyeval.context(), maybe by _.extend-ing ``result_context`` into ``evaluation_context`` at the *top* of the reduction function rather than at its bottom? bzr revid: xmo@openerp.com-20130128130640-ksyvxvx6rlc4820n |
||
|---|---|---|
| .. | ||
| boot.js | ||
| chrome.js | ||
| corelib.js | ||
| coresetup.js | ||
| data.js | ||
| data_export.js | ||
| dates.js | ||
| formats.js | ||
| pyeval.js | ||
| search.js | ||
| test_support.js | ||
| testing.js | ||
| view_form.js | ||
| view_list.js | ||
| view_list_editable.js | ||
| view_tree.js | ||
| views.js | ||