[RTK] Preserve non-JSON error responses

[yi-nuo426]

Summary

• add a shared RTK response handler for Meshery and cloud base queries
• parse JSON when possible and return raw text otherwise
• avoid PARSING_ERROR failures when APIs return non-JSON error bodies

Testing

• npm run build

[Copilot]

Pull request overview

This PR updates the shared RTK Query base queries for both Meshery and Cloud to preserve non-JSON response bodies (especially error bodies) by introducing a custom responseHandler that attempts JSON parsing and falls back to returning raw text.

Changes:

• Added a shared parseBaseQueryResponse handler to parse JSON when possible and otherwise return raw response text.
• Wired the custom responseHandler into both Cloud and Meshery fetchBaseQuery configurations.

[Copilot]

parseBaseQueryResponse attempts JSON.parse on every non-empty body, regardless of Content-Type. This will coerce valid JSON scalars like 0, true, or null into non-string values even when the server returns text/plain (your OpenAPI specs define several text/plain responses as type: string). Consider keying JSON parsing off response.headers.get('content-type') (e.g., application/json / +json) or at least a cheap heuristic like trim() + leading {/[ to avoid mis-parsing plain-text responses; also treat whitespace-only bodies as empty via trim().

Suggested change

	if (!text) {
	return null;
	}
	try {
	return JSON.parse(text);
	} catch {
	return text;
	}
	const trimmedText = text.trim();
	if (!trimmedText) {
	return null;
	}
	const contentType = response.headers.get("content-type")?.toLowerCase() ?? "";
	const isJsonResponse = contentType.includes("application/json") || contentType.includes("+json");
	if (isJsonResponse) {
	try {
	return JSON.parse(text);
	} catch {
	return text;
	}
	}
	return text;

[gemini-code-assist]

Code Review

This pull request introduces a custom response handler, parseBaseQueryResponse, to manage empty or non-JSON responses for the RTK Query base queries. The feedback suggests refining the error handling within this function to specifically catch SyntaxError during JSON parsing, ensuring that other potential runtime errors are not inadvertently suppressed.

[gemini-code-assist]

The parseBaseQueryResponse function uses a generic try-catch block that catches all errors. It is better to specifically catch SyntaxError when parsing JSON to avoid masking other potential runtime errors.

const parseBaseQueryResponse = async (response: Response) => {
  const text = await response.text();

  if (!text) {
    return null;
  }

  try {
    return JSON.parse(text);
  } catch (e) {
    if (e instanceof SyntaxError) {
      return text;
    }
    throw e;
  }
};