Split EDI repo (?)#99
Conversation
There was a problem hiding this comment.
I'm not an EDI maintainer but I drop my opinion/quesitons anyway...
Since the split in v16 with edi-framework, the edi repo only contains 20 modules, some of them are glue modules or the implementation of different standards in different apps (example EDIFACT: base_edifact with their sale order and invoice implementations). What is the benefit on separating these modules that are so closely related?
Maybe I'm not realizing of some extra complexity, so my apologies :)
My 2 cents.
|
@LoisRForgeFlow maybe you are right regarding the size from 16 on. However, my feeling is that it would cleaner and clearer.... I have no strong argument tho :) |
|
@simahawk If a split is needed, I think it makes more sense to do it by standard, like edi-edifact, edi-ubl, etc. The rationale for splitting would be much more easy to understand and apply IMO. E.g: What if you develop edifact_repair? would you need to ask for a new repo edi-repair? |
I would keep it as it is so far |
|
I would prefer to not split it. |
|
Ok gents! Thanks for you feedback 🙏 |
4 participants
The EDI repo is quite big and has a huge scope... Shall we take the chance to split it while on v18 there's no specific module migrated?
@OCA/edi-maintainers