add handling for extension base without children #1135
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
|
ok, finally, it looks good. |
|
@KnutEdelbert please remove the change to package-lock.json |
as @jsdevel said: "please remove the change to package-lock.json". It's done.
|
@jsdevel as you wish - it's deleted |
added 2 commits
January 28, 2021 17:07
|
ok, i think it was better to revert the file instead of deleting it.... |
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.
When parsing the wsdl, the trace don't recognize the reference in the base attribute of an ExtensionElement without child nodes, when it comes to findChildSchemaObject. It should be handled like the type attribute on ElementElements