Components
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.
Table of contents
Usage
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 classes provided by odoo.addons.component.tests.common:
TransactionComponentCase
SavepointComponentCase
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.
Changelog
Next
12.0.1.0.0 (2018-10-02)
[MIGRATION] from 11.0 branched at rev. 324e006
Bug Tracker
Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us smashing it by providing a detailed and welcomed feedback.
Do not contact contributors directly about support or help with technical issues.
Credits
Contributors
Guewen Baconnier <guewen.baconnier@camptocamp.com>
Laurent Mignon <laurent.mignon@acsone.eu>
Maintainers
This module is maintained by the OCA.
OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.
Current maintainer:
This module is part of the OCA/connector project on GitHub.
You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.
Metadata
Release files for odoo13-addon-component 13.0.1.2.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| odoo13_addon_component-13.0.1.2.1-py3-none-any.whl | Python 3 | none | any | Details for odoo13_addon_component-13.0.1.2.1-py3-none-any.whl |
Release files / odoo13_addon_component-13.0.1.2.1-py3-none-any.whl
| Download URL | odoo13_addon_component-13.0.1.2.1-py3-none-any.whl |
|---|---|
| Size | 59.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4bd4e015a1cbc2b0dbac2ca9332502711cc1b3c09cd53c48eb5a9c9260b0ae55
|
|
BLAKE2b-256 checksum How to use checksums |
f0ec333e38c486f4dc191c8c8dd46955c678686e9ba7983f859351473de8b332
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.8.5
|
Security for odoo13-addon-component 13.0.1.2.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.