[19.0][IMP] edi_*_oca: skip exchange types w/o handler in cron domains#273
[19.0][IMP] edi_*_oca: skip exchange types w/o handler in cron domains#273HviorForgeFlow wants to merge 4 commits into
Conversation
|
Wondering: why is it possible to handle an exc type w/o handler? It should be validated beforehand... We should make specific validators required based on the direction. |
11c86d7 to
960d553
Compare
8d1870f to
c20e67c
Compare
That makes more sense, cleaner implementation, thanks for the advice |
c20e67c to
bcb249e
Compare
4db716b to
2134f83
Compare
|
@simahawk it follows your suggested approach |
|
This PR has the |
|
@HviorForgeFlow I think you miss the part "specific validators required based on the direction." What about adding validation and fixing the data the you have?
WDYT? |
|
@HviorForgeFlow ping :) |
|
Proposal on adding validators and constraints to the exchange type as you were suggesting @simahawk |
f9cdf6b to
7eb70b3
Compare
6e132ca to
63cfd44
Compare
c23fb91 to
a4b5e52
Compare
The new _check_direction_handlers constraint broke installation with demo data and several test suites. Add edi.oca.handler.noop in edi_core_oca, reference it from the affected demo exchange types, and make test exchange types default to it when no handler is registered.
e9a6fd8 to
8d889b1
Compare
|
@simahawk could you check? |
Noticed while developing that when a exchange type is not linked to a handler and the EDINotImplementedError is raised, a DB rollback takes places undoing all previous work.
To ensure that skipping not handled exchanges does not break anything outside the cron scope I had to slightly change the exchange_generate_send method.
CC @etobella @simahawk @ForgeFlow