kie-issues#665: xml-parser-ts
Doesn't manage Complex Types with Simple Content
#2039
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.
Closes apache/incubator-kie-issues#665
The problem:
xml-parser-ts
it's not able to manage Complex Types with Simple Content, please consider the following example:XML
<rawValue class="string">Above speed limit: 10km/h and 30 km/h</rawValue>
XSD
Generated type:
Fields are missing
At Runtime:
The solution (kudos to @tiagobento )
For any text value, we are going to provide a new
__$$text
. This will impact any TextContent, in order to unify the text content management. That means, any simple type that previously held text content, now holds an Object with a__$$text
field.Current generated type:
Fields are missing
At Runtime: