Closed jcleung5549 closed 5 years ago
We ran into the same problem with the
@jcleung5549 I don't think this is an issue with the tool; I think CSDLParser needs to be updated to allow <Annotation>
within <Annotation>
.
While annotations within annotation is still the case, it might no longer be the case when generating the new style of "PropertyValue" or "Property" tags inside of annotation. However, Description tags that have Odata.Description
and LongDescription
would still create Annotations
ex:
<Record>
<Annotation Term="RedfishYang.revision" String="2018-04-24">
<Annotation Term="OData.Description" String="Clarified order of ACL evaluation."/>
<Annotation Term="OData.LongDescription" String="Clarified order of ACL evaluation."/>
<PropertyValue Property="reference" String="1.0.1"/>
</Annotation>
</Record>
Should embedded description records just be referred to by their YANG tag?
Since we have expectations for how certain annotations are used in Redfish, I think we'd still want to use the existing OData.Description and OData.LongDescription annotations. It would give us better mapping alignment between YANG and Redfish.
Newer version of CSDLParser has been pushed to allow for Annotations in Annotations and the Travis package list in the branch has been updated to use the newer version.
Would like to keep this open until we positively confirm this is resolved.
No longer seeing with YANG-2019. Waiting for a clean Travis run, before closing this issue.
Travis is not longer generating this error.
Travis complains when an element is within another element.