[FIX] somebody renamed classes without fixing the corresponding autodoc invocation

bzr revid: xmo@openerp.com-20140116144957-j2no6ls83vfxtgbk
This commit is contained in:
Xavier Morel 2014-01-16 15:49:57 +01:00
parent 2e43125353
commit ff51574fae
3 changed files with 7 additions and 14 deletions

View File

@ -252,5 +252,4 @@ texinfo_documents = [
# Example configuration for intersphinx: refer to the Python standard library. # Example configuration for intersphinx: refer to the Python standard library.
intersphinx_mapping = { intersphinx_mapping = {
'python': ('http://docs.python.org/', None), 'python': ('http://docs.python.org/', None),
'openerpweb': ('http://doc.openerp.com/trunk/developers/web', None),
} }

View File

@ -12,26 +12,20 @@ Server actions
.. currentmodule:: openerp.addons.base.ir.ir_actions .. currentmodule:: openerp.addons.base.ir.ir_actions
.. autoclass:: actions_server .. autoclass:: ir_actions_server
:noindex: :members: run, _get_states
Adding a new sever action Adding a new sever action
------------------------- -------------------------
The ``state`` field holds the various available types of server action. In order The ``state`` field holds the various available types of server action. In order
to add a new server action, the first thing to do is to override the ``_get_states`` to add a new server action, the first thing to do is to override the :meth:`~.ir_actions_server._get_states`
method that returns the list of values available for the selection field. method that returns the list of values available for the selection field.
.. automethod:: actions_server._get_states The method called when executing the server action is the :meth:`~.ir_actions_server.run` method. This
:noindex:
The method called when executing the server action is the ``run`` method. This
method calls ``run_action_<STATE>``. When adding a new server action type, you method calls ``run_action_<STATE>``. When adding a new server action type, you
have to define the related method that will be called upon execution. have to define the related method that will be called upon execution.
.. automethod:: actions_server.run
:noindex:
Changelog Changelog
--------- ---------

View File

@ -911,10 +911,10 @@ class ir_actions_server(osv.osv):
self.pool[action.model_id.model].write(cr, uid, [context.get('active_id')], {action.link_field_id.name: res_id}) self.pool[action.model_id.model].write(cr, uid, [context.get('active_id')], {action.link_field_id.name: res_id})
def run(self, cr, uid, ids, context=None): def run(self, cr, uid, ids, context=None):
""" Run the server action. For each server action, the condition is """ Runs the server action. For each server action, the condition is
checked. Note that A void (aka False) condition is considered as always checked. Note that a void (``False``) condition is considered as always
valid. If it is verified, the run_action_<STATE> method is called. This valid. If it is verified, the run_action_<STATE> method is called. This
allows easy inheritance of the server actions. allows easy overriding of the server actions.
:param dict context: context should contain following keys :param dict context: context should contain following keys