[19.0][MIG] edi_endpoint_oca: Migration to V19#262
Open
[19.0][MIG] edi_endpoint_oca: Migration to V19#262
Conversation
Block archiving of backends if they have active endpoints exposed.
* more efficient w/ read_group * consider only active records explicitly
I don't know why but when test_edi_endpoint runs before these tests the rollback of the exception catched within the test `test_archive_check` make the controller lookup fail. Since the whole routing registry machinery is going to be refactored in OCA/edi#633 let's survive w/ this forced registration for now.
Former version of `endpoint_route_handler` had a major flaw: routing rule registry was not properly shared across workers forcing us to restart the instance to make sure all envs were inline w/ it. This change adapts edi_endpoint_oca to the new version which contains some refactoring.
It's very handy to know which endpoint generated a record.
Moved from OCA/edi repository
The new mixin view won't be affected by weird extensions. Requires OCA/web-api#56 Solves conflict w/ OCA/web-api-contrib#1
Currently translated at 1.9% (1 of 51 strings) Translation: edi-framework-16.0/edi-framework-16.0-edi_endpoint_oca Translate-URL: https://translation.odoo-community.org/projects/edi-framework-16-0/edi-framework-16-0-edi_endpoint_oca/it/
edi.endpoint views must be independent that's why primary mode is used. endpoint.endpoint views might be polluted by other modules: this change ensures they are isolated. Depends on OCA/web-api#87
If record field value is already True, impossible to sync the registry
A new route parameter has been introduced and for existing endpoints to work OOTB we must resync.
Currently translated at 100.0% (51 of 51 strings) Translation: edi-framework-18.0/edi-framework-18.0-edi_endpoint_oca Translate-URL: https://translation.odoo-community.org/projects/edi-framework-18-0/edi-framework-18-0-edi_endpoint_oca/it/
Setting the file content after creating the record might lead to errors when the exchange type is has quick_exec enabled. That's because the backend will try to process the file immediately on create but there's no file content yet. Just populate the file content right away.
yankinmax
force-pushed
the
19.0-mig-edi_endpoint_oca
branch
4 times, most recently
from
eb5dc16 to
13d45a1
Compare
yankinmax
force-pushed
the
19.0-mig-edi_endpoint_oca
branch
from
6cc60cd to
591bd6e
Compare
ivantodorovich
approved these changes
Apr 6, 2026
grindtildeath
approved these changes
Apr 7, 2026
simahawk
requested changes
Apr 14, 2026
|
|
||
| @unittest.skipIf(os.getenv("SKIP_HTTP_CASE"), "EDIEndpointHttpCase skipped") | ||
| class EDIEndpointHttpCase(HttpCase): | ||
| class EDIEndpointHttpCase(HttpCase, CommonEDIEndpoint): |
Contributor
There was a problem hiding this comment.
This is mixing 2 different base test classes. We might have weird behaviors.
Options:
- import setup methods and use them directly in setUpClass
- do not make
CommonEDIEndpointinherit fromTransactionCaseand make it a bare mixin class w/ a_setup_endpoint_envgeneral setup method that you can call here insetUpClass
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
12 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Standard migration.
Depends on:
This PR is opened to speed up migration to 19.0.