@mcp-abap-adt/adt-clients 36.0.0 → 36.0.1

package/README.md

@@ -948,8 +948,10 @@ pair you choose. Two pure functions over the error are exported:
 - `extractSupportedAccept(error)` — the list SAP writes into its `406` body,
   `Accepted content types: …` (often empty; measured on an on-premise system).
   It reads no header and no other text.
-- `extractSupportedContentType(error)` — the types a `415` names (its headers
-  and body; unchanged).
+- `extractSupportedContentType(error)` — the list SAP writes into its `415`
+  body, `Supported Media Types: …` (absent from a bare `Unsupported Media
+  Type`; measured on an on-premise system). It reads no header — the `415`'s
+  own `content-type` is its error document's — and no other text (36.0.1).
 
 ```typescript
 import { extractSupportedAccept } from '@mcp-abap-adt/adt-clients';

package/dist/utils/supportedMediaTypes.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"supportedMediaTypes.d.ts","sourceRoot":"","sources":["../../src/utils/supportedMediaTypes.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;GAUG;AAmBH,wBAAgB,sBAAsB,CAAC,KAAK,EAAE,OAAO,GAAG,MAAM,EAAE,CAsB/D;AAED,wBAAgB,2BAA2B,CAAC,KAAK,EAAE,OAAO,GAAG,MAAM,EAAE,CAsCpE"}
+{"version":3,"file":"supportedMediaTypes.d.ts","sourceRoot":"","sources":["../../src/utils/supportedMediaTypes.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;GAUG;AA0DH,wBAAgB,sBAAsB,CAAC,KAAK,EAAE,OAAO,GAAG,MAAM,EAAE,CAE/D;AAED,wBAAgB,2BAA2B,CAAC,KAAK,EAAE,OAAO,GAAG,MAAM,EAAE,CAKpE"}

package/dist/utils/supportedMediaTypes.js

@@ -24,16 +24,31 @@ exports.extractSupportedContentType = extractSupportedContentType;
  * URI (`www.sap.com/abapxml`, `types/communicationframework`) on every 406.
  */
 const ACCEPTED_CONTENT_TYPES = 'Accepted content types:';
+/**
+ * The text SAP's 415 puts before the types it accepts as a body.
+ *
+ * Measured on an on-premise system: SAP answers a 415 with its exception
+ * document (`content-type: application/xml`, the document's own type), whose
+ * message reads "Unsupported Media Type. Supported Media Types: …" — or a bare
+ * "Unsupported Media Type". Only that list is read. Until 36.0.0 the parser
+ * also read the response's headers and every `type/subtype` in the body, so it
+ * answered `application/xml` and two fragments of the document's namespace URI
+ * before the type SAP named.
+ */
+const SUPPORTED_MEDIA_TYPES = 'Supported Media Types:';
 /** Where the list after the marker ends: the element, an attribute or the line. */
 const LIST_ENDS = ['<', '"', '\n'];
-function extractSupportedAccept(error) {
-    const e = error;
-    const data = e?.response?.data;
-    const text = typeof data === 'string' ? data : data ? JSON.stringify(data) : '';
+/** The body of a refusal as text. */
+function bodyText(error) {
+    const data = error?.response?.data;
+    return typeof data === 'string' ? data : data ? JSON.stringify(data) : '';
+}
+/** Every type listed after `marker` in `text`, in order, each once. */
+function listedAfter(text, marker) {
     const types = new Set();
-    let at = text.indexOf(ACCEPTED_CONTENT_TYPES);
+    let at = text.indexOf(marker);
     while (at !== -1) {
-        const start = at + ACCEPTED_CONTENT_TYPES.length;
+        const start = at + marker.length;
         let end = text.length;
         for (const stop of LIST_ENDS) {
             const found = text.indexOf(stop, start);
@@ -45,40 +60,16 @@ function extractSupportedAccept(error) {
             if (type)
                 types.add(type);
         }
-        at = text.indexOf(ACCEPTED_CONTENT_TYPES, end);
+        at = text.indexOf(marker, end);
     }
     return Array.from(types);
 }
+function extractSupportedAccept(error) {
+    return listedAfter(bodyText(error), ACCEPTED_CONTENT_TYPES);
+}
 function extractSupportedContentType(error) {
-    const e = error;
-    if (e?.response?.status !== 415) {
+    if (error?.response?.status !== 415) {
         return [];
     }
-    const types = new Set();
-    const headers = (e?.response?.headers || {});
-    const headerCandidates = [
-        headers['content-type'],
-        headers['x-sap-adt-supported-content-type'],
-        headers['supported-content-type'],
-    ];
-    for (const value of headerCandidates) {
-        if (typeof value === 'string') {
-            value
-                .split(',')
-                .map((entry) => entry.trim())
-                .filter(Boolean)
-                .forEach((entry) => {
-                types.add(entry);
-            });
-        }
-    }
-    const data = e?.response?.data;
-    const text = typeof data === 'string' ? data : data ? JSON.stringify(data) : '';
-    if (text) {
-        const matches = text.match(/[a-zA-Z0-9.+-]+\/[a-zA-Z0-9.+-]+(?:;[^,\s]+)?/g) || [];
-        for (const match of matches) {
-            types.add(match);
-        }
-    }
-    return Array.from(types).filter(Boolean);
+    return listedAfter(bodyText(error), SUPPORTED_MEDIA_TYPES);
 }

package/docs/usage/MIGRATION-36.md

@@ -140,7 +140,12 @@ nothing else. Until 35.x it also read five headers and every `type/subtype` in
 the body, which answered two fragments of the exception's namespace URI
 (`www.sap.com/abapxml`, `types/communicationframework`) for every `406`. A
 consumer that fed it a `406` carrying the types in a header gets `[]` now.
-`extractSupportedContentType` (`415`) is unchanged.
+`extractSupportedContentType` (`415`) was unchanged in 36.0.0; since 36.0.1
+it reads only SAP's list the same way — `Supported Media Types: …` in the
+`415` body (measured on an on-premise system), no header and no other text.
+Until then it answered the `415`'s own `content-type` (`application/xml`, the
+error document's type) and the two namespace fragments before the type SAP
+named.
 
 ## The completed pairs, measured
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mcp-abap-adt/adt-clients",
-  "version": "36.0.0",
+  "version": "36.0.1",
   "description": "ADT clients for SAP ABAP systems - AdtClient and AdtRuntimeClient",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",