Added xml counterparts for all examples #5
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
MarcusRost
approved these changes
Nov 1, 2023
MarcusRostSAP
added a commit
that referenced
this pull request
Feb 7, 2024
* reformatted for linting bot * Added xml counterparts for all examples (#5) * added xml counterparts for every json file * Changed test constants to include xmlpath * Add tests for xml code * added some test utils, but xml seems broken * some parser configs * Reformat tests * Removed unecessary print statement * Included more variants of XOR gateways * Removed file * reformatting * Reformatting according to linter * Linting * Linting --------- Co-authored-by: MarcusRostSAP <marcus.rost@hotmail.com> --------- Co-authored-by: MarcusRostSAP <marcus.rost@hotmail.com>
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.
Related to issue signavio#14, when the tests and xml files were added, it turned out that the parser interpreted xml and json very differently.