POCO Annotation from EDI Documentation Examples
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 490
- Forks
- 173
- PR merge metrics
- No merged PRs in 30d
Description
I need to deserialize the following EDI format/files into POCO classes.
https://static.ark.org/eeuploads/adhe/TS130.pdf
I'm a .Net developer but brand new to EDI. Are there some examples on how to structure and annotate POCO's from the EDI documentation? I've looked at the example POCO's here but it's still not clear how to translate from the documentation to the classes.
Thanks.
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
Start with the linked TS130 PDF and the repository's existing example POCO classes. Compare the EDI documentation with those examples to identify what translation guidance is missing. Done means adding clear POCO annotation examples or documentation for this EDI format, with enough context for a .NET developer new to EDI to follow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100