The Elasticsearch-backed NodeNorm publishes a 200 response with no description, which OpenAPI 3.x requires on every response object, so the document fails validation:
'description' is a required property
Failed validating 'required' in schema['properties']['paths']['patternProperties']['^/']['else']
['properties']['get']['properties']['responses']['patternProperties']['^[1-5](?:[0-9]{2}|XX)$']['else']
The offender is GET /get_allowed_conflations, whose 200 response carries content but no description.
Affected (checked 2026-08-31), version 1.0.0 in both:
The Redis-backed deployments do not have this problem; they fail validation for a different reason, filed separately as #409 (which the Elasticsearch document also carries).
To reproduce:
import requests
from openapi_spec_validator import validate
validate(requests.get("https://nodenorm-es.test.transltr.io/webapp/openapi.json").json())
Found by test_openapi_json in TranslatorSRI/babel-validation.
The Elasticsearch-backed NodeNorm publishes a
200response with nodescription, which OpenAPI 3.x requires on every response object, so the document fails validation:The offender is
GET /get_allowed_conflations, whose200response carriescontentbut nodescription.Affected (checked 2026-08-31), version 1.0.0 in both:
The Redis-backed deployments do not have this problem; they fail validation for a different reason, filed separately as #409 (which the Elasticsearch document also carries).
To reproduce:
Found by
test_openapi_jsonin TranslatorSRI/babel-validation.