no reporting after validation or parsing about amf

[sichvoge]

Reduced the example to:

#%RAML 1.0

version: 1.0

/customers:
  displayName: Customer Resource
  /{customer_id}:
    get:
      description: Returns customer data
      responses:
        200:
          body:
            application/json:

What's strange is that moving the get node into /customers: and remove the resource with the URI parameter, it works as expected and I do get:

===========================
None
===========================
{
  "@type": "http://www.w3.org/ns/shacl#ValidationReport",
  "http://www.w3.org/ns/shacl#conforms": false,
  "http://www.w3.org/ns/shacl#result": [
    {
      "@type": "http://www.w3.org/ns/shacl#ValidationResult",
      "http://www.w3.org/ns/shacl#resultSeverity": {
        "@id": "http://www.w3.org/ns/shacl#Violation"
      },
      "http://www.w3.org/ns/shacl#focusNode": {
        "@id": "file:/test.raml#/web-api"
      },
      "http://www.w3.org/ns/shacl#resultPath": {
        "@id": "http://schema.org/name"
      },
      "http://www.w3.org/ns/shacl#resultMessage": "API name must be a single value",
      "http://www.w3.org/ns/shacl#sourceShape": {
        "@id": "http://raml.org/vocabularies/amf/parser#WebAPI-name-minCount"
      }
    }
  ]
}

[sichvoge]

Seems like AMF does not like URI parameters like /{customer_id}. Having another resource as sub-resource also works.

#%RAML 1.0

version: 1.0

/customers:
  displayName: Customer Resource
  get:
    description: Returns customer data
    responses:
      200:
        body:
          application/json:
  /Accounts:
    get:
      description: Returns a collection of accounts.
      responses:
        200:
          body:
            application/json: