[ADD] Edi Ediversa Repository#102
Merged
simahawk merged 1 commit intoOCA:masterfrom Jul 17, 2025
Merged
Conversation
Contributor
Author
pedrobaeza
approved these changes
Jul 16, 2025
etobella
approved these changes
Jul 16, 2025
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
5 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.
Following the conversation held in this PR (OCA/edi#1163 (comment)), I am proposing the opening of an EDI sub-repository for the ediversa supplier.
On the other hand, I've been reviewing the discussion about separating the EDI repository, but it was ultimately discarded (#99). For my part, I see sense in creating sub-repositories, since otherwise, there would be a very large single repository. It makes sense to leave the EDI repository for generic things, and on the other hand, the sub-repositories for each supplier. For external searches, it's possibly better too.