EDIFACT D96B addition
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 490
- Forks
- 173
- PR merge metrics
- No merged PRs in 30d
Description
Hey I would like to improve your examples by the D96B standard. Thought about a PR but with attention to your ToDo entry No. 3 ("Create a seperate package (or packages per EDI Format)...") I guess the separated version is better for now.
The attached file contains the full ORDERS document type - as well as all segments in use by. For a work project I'll have to implement ORDERS, INVOICE and ORDRSP in the next days - will add them at given time. Some preperation is already done.
As this is a "pull-out" of a WIP project it's source and naming is far from perfect and in some cases quite specific. But I guess I'm allowed to delegate this work to someone else :)
Service.Intermediate.Edifact.D96B.zip
I'm open for questions and improvements - also if someone could write some tests.
Best regards
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the repository's existing EDIFACT examples and TODO entry No. 3, then inspect the attached Service.Intermediate.Edifact.D96B.zip for the ORDERS document type and segments. Confirm how a separate D96B package or example set should fit the current structure. Done means the D96B ORDERS material is integrated consistently and covered by tests, with later INVOICE and ORDRSP work treated separately.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- data-engineering
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100