From 523709281c22469d48887c1b0e9ac9f9c530313b Mon Sep 17 00:00:00 2001 From: Thomas Frauenstein Date: Tue, 25 Jun 2024 19:40:23 +0200 Subject: [PATCH] Update compatibility.adoc --- chapters/compatibility.adoc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/chapters/compatibility.adoc b/chapters/compatibility.adoc index 6f489e1e..3b39bb8f 100644 --- a/chapters/compatibility.adoc +++ b/chapters/compatibility.adoc @@ -315,7 +315,7 @@ delivery_methods: ---- *Note:* {x-extensible-enum} is a proprietary extension of the JSON Schema standard that -will be ignored by most tools. +is e.g. visible via Swagger UI and ignored by most tools. See <<240>> about enum value naming conventions. @@ -329,6 +329,6 @@ must implement a fallback / default behavior to handle unknown new enum values - API owners must take care to extend enums in a compatible way that does not change the semantics of already existing enum values, for instance, do not split an old enum value into two new enum values. Services should only extend {x-extensible-enum} ranges, and only accept -and return values listed in the latest API version which needs to be updated first before -providing new values -- see also <<107>>. +and return values listed in the API definition, i.e. the API definition needs to be updated first +before the service accepts/returns new values -- see also <<107>>.