mirror of
https://github.com/bringout/oca-technical.git
synced 2026-04-18 18:32:03 +02:00
Initial commit: OCA Technical packages (595 packages)
This commit is contained in:
commit
2cc02aac6e
24950 changed files with 2318079 additions and 0 deletions
|
|
@ -0,0 +1,3 @@
|
|||
* Guewen Baconnier <guewen.baconnier@camptocamp.com>
|
||||
* Laurent Mignon <laurent.mignon@acsone.eu>
|
||||
* Simone Orsi <simone.orsi@camptocamp.com>
|
||||
|
|
@ -0,0 +1,8 @@
|
|||
This module implements a component system and is a base block for the Connector
|
||||
Framework. It can be used without using the full Connector though.
|
||||
|
||||
Documentation: http://odoo-connector.com/
|
||||
|
||||
You may also want to check the `Introduction to Odoo Components`_ by @guewen.
|
||||
|
||||
.. _Introduction to Odoo Components: https://dev.to/guewen/introduction-to-odoo-components-bn0
|
||||
|
|
@ -0,0 +1,34 @@
|
|||
.. [ The change log. The goal of this file is to help readers
|
||||
understand changes between version. The primary audience is
|
||||
end users and integrators. Purely technical changes such as
|
||||
code refactoring must not be mentioned here.
|
||||
|
||||
This file may contain ONE level of section titles, underlined
|
||||
with the ~ (tilde) character. Other section markers are
|
||||
forbidden and will likely break the structure of the README.rst
|
||||
or other documents where this fragment is included. ]
|
||||
|
||||
16.0.1.0.0 (2022-10-04)
|
||||
~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
* [MIGRATION] from 15.0
|
||||
|
||||
15.0.1.0.0 (2021-11-25)
|
||||
~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
* [MIGRATION] from 14.0
|
||||
|
||||
14.0.1.0.0 (2020-10-22)
|
||||
~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
* [MIGRATION] from 13.0
|
||||
|
||||
13.0.1.0.0 (2019-10-23)
|
||||
~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
* [MIGRATION] from 12.0
|
||||
|
||||
12.0.1.0.0 (2018-10-02)
|
||||
~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
* [MIGRATION] from 11.0 branched at rev. 324e006
|
||||
|
|
@ -0,0 +1,32 @@
|
|||
As a developer, you have access to a component system. You can find the
|
||||
documentation in the code or on http://odoo-connector.com
|
||||
|
||||
In a nutshell, you can create components::
|
||||
|
||||
|
||||
from odoo.addons.component.core import Component
|
||||
|
||||
class MagentoPartnerAdapter(Component):
|
||||
_name = 'magento.partner.adapter'
|
||||
_inherit = 'magento.adapter'
|
||||
|
||||
_usage = 'backend.adapter'
|
||||
_collection = 'magento.backend'
|
||||
_apply_on = ['res.partner']
|
||||
|
||||
And later, find the component you need at runtime (dynamic dispatch at
|
||||
component level)::
|
||||
|
||||
def run(self, external_id):
|
||||
backend_adapter = self.component(usage='backend.adapter')
|
||||
external_data = backend_adapter.read(external_id)
|
||||
|
||||
|
||||
In order for tests using components to work, you will need to use the base
|
||||
class provided by `odoo.addons.component.tests.common`:
|
||||
|
||||
* `TransactionComponentCase`
|
||||
|
||||
There are also some specific base classes for testing the component registry,
|
||||
using the ComponentRegistryCase as a base class. See the docstrings in
|
||||
`tests/common.py`.
|
||||
Loading…
Add table
Add a link
Reference in a new issue