• Hide

      I propose to make the grammar consistent with the code examples by removing the "import_name" from both the single-line and multi-line grammars. The following example (adapted from section 3.5.7.3) shows how this would get used:

      imports:

      Show
      I propose to make the grammar consistent with the code examples by removing the "import_name" from both the single-line and multi-line grammars. The following example (adapted from section 3.5.7.3) shows how this would get used: imports: path1/path2/some_defs.yaml file: path1/path2/file2.yaml repository: my_service_catalog namespace_uri: http://mycompany.com/tosca/1.0/platform namespace_prefix: mycompany

      I finally got around to implementing the extended "imports" grammar and noticed issues with both the single-line and the multi-line grammar for imports. Imports grammar is as follows:

      3.5.7.2.1 Single-line grammar:
      <import_name>: <file_URI>

      3.5.7.2.2 Multi-line grammar
      <import_name>:
      file: <file_URI>
      repository: <repository_name>
      namespace_uri: <definition_namespace_uri>
      namespace_prefix: <definition_namespace_prefix>

      In both cases, the grammar specifies that imports have an "import_name". However, none of the YAML templates in the spec ever use such an import_name, and in any event, since there really isn't a use for such a name enforcing it would result in an unnecessary burden.

            Assignee:
            Matthew Rutkowski (Inactive)
            Reporter:
            Chris Lauwers (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: