[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (TOSCA-301) Wrong grammar definition pointing to non existent type
[ https://issues.oasis-open.org/browse/TOSCA-301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62894#comment-62894 ] Luca Gioppo commented on TOSCA-301: ----------------------------------- The hyperlink in the doc should point to the proper line "below" so for property_type to the 1373 line and not to the YAML TYPE part. User could get confised and expecting a property_type where there is none. This problem could be worse in case of part of the text ending in another page so you really do not know that a few lines below you are going to find the definition not of the property_type but of the "pseudo values". Is really confusing. > Wrong grammar definition pointing to non existent type > ------------------------------------------------------ > > Key: TOSCA-301 > URL: https://issues.oasis-open.org/browse/TOSCA-301 > Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC > Issue Type: Bug > Components: Profile-YAML > Affects Versions: V1.1_CSD04 > Reporter: Luca Gioppo > > At line 1369 we have the grammar definition of properties and we have: > <property_name>: > type: <property_type> > description: <property_description> > required: <property_required> > default: <default_value> > status: <status_value> > constraints: > - <property_constraints> > It should be more proper to write: > <property_name>: > type: <YAML Type> > description: <description definition> > required: <YAML_BOOLEAN> > default: <default_value> > status: <property_status_value> > etc.... > We do not have ANY "property_type" but a "YAML type" -- This message was sent by Atlassian JIRA (v6.2.2#6258)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]