Skip to content

GET /get_allowed_conflations has a 200 response with no description, failing OpenAPI validation on the -es deployments #410

Description

@gaurav

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.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions