You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
loads a valid external reference that should work but creates creates a 500 - Internal Server Error response:
{
"title":"Internal Server Error",
"status":500,
"detail":"check invocation failed: id=Z001 title=Path parameters validation checkName=checkSchemaOrContentProperty reason=java.lang.NullPointerException: parameter.name must not be null"
}
The details of the stack trace are
java.lang.RuntimeException: check invocation failed: id=Z001 title=Path parameters validation checkName=checkSchemaOrContentProperty reason=java.lang.NullPointerException: parameter.name must not be null
at org.zalando.zally.core.RulesValidator.invoke(RulesValidator.kt:63) ~[zally-core-2.1.1-SNAPSHOT.jar!/:na]
at org.zalando.zally.core.RulesValidator.validate(RulesValidator.kt:40) ~[zally-core-2.1.1-SNAPSHOT.jar!/:na]
at org.zalando.zally.core.CompositeRulesValidator.validate(CompositeRulesValidator.kt:9) ~[zally-core-2.1.1-SNAPSHOT.jar!/:na]
at org.zalando.zally.apireview.ApiViolationsController.validate(ApiViolationsController.kt:47) ~[classes!/:na]
at jdk.internal.reflect.GeneratedMethodAccessor262.invoke(Unknown Source) ~[na:na]
...
Caused by: java.lang.NullPointerException: parameter.name must not be null
at org.zalando.zally.ruleset.zally.PathParameterRule.checkSchemaOrContentProperty(PathParameterRule.kt:47) ~[zally-ruleset-zally-2.1.1-SNAPSHOT.jar!/:na]
... 98 common frames omitted
The failure looks like an authorization problem, however, while on first sight the referenced location looks fine, it contains another local reference that may create problems:
in: body
name: body
description: "Consent object"
required: true
schema:
$ref: "#/definitions/Consents"
The problem here is that in: body is not allowed in this parameter list. Consequently, the parser seems to filter resulting in an empty parameter array element, which results in a null-name as the NPE is telling. Note: referencing in: query parameter is working fine, e.g. Services.
The text was updated successfully, but these errors were encountered:
Following simple API example
loads a valid external reference that should work but creates creates a
500 - Internal Server Error
response:The details of the stack trace are
The failure looks like an authorization problem, however, while on first sight the referenced location looks fine, it contains another local reference that may create problems:
The problem here is that
in: body
is not allowed in this parameter list. Consequently, the parser seems to filter resulting in anempty
parameter array element, which results in anull
-name as the NPE is telling. Note: referencingin: query
parameter is working fine, e.g.Services
.The text was updated successfully, but these errors were encountered: