Wip edifact object tree #3
Merged
Conversation
This file contains 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
added 9 commits
August 31, 2020 19:53
…he parsed segments. Currently only INVOIC and DESADV segments are supported.
…act definition pages to generate the JSON structure objects used while parsing/validation
…re streamlined directories to fix the eslint issue constantly reported but to only export the actual source classes. Problem currently reported for index.ts is hack-fixed by importing some of the exports during the interchange creation as eslint requires all of the linted files to be included -> chicken/egg problem ...
…tail values and futher stuff
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR will add a way to generate message structure files by parsing the official UNECE website, which hosts the actual Edifact message type, segment and element specifications
Further this PR will add a way to generate an object-tree for a parsed Edifact interchange, which follows the structure definition of a message interchange.
Last but not least, this PR will also change the Validator implementation to ignore unknown segments and elements by default and only throw an error on such segments/elements if a strict validation was requested