Problem
updateSchema in src/services/serverless-schema-management.service.ts has its own inline error handler (lines 347-356) that does not call handleSchemaError. It uses JSON.stringify(error.response.data) instead of extracting the human-readable message.
All other methods in this service correctly delegate to handleSchemaError, which extracts data.message, data.error, plain-text strings, etc.
Expected behavior
updateSchema should delegate to handleSchemaError like the other methods, so Cloud Serverless {"code":"...","message":"..."} errors are surfaced as readable messages instead of raw JSON blobs.
Affected code
src/services/serverless-schema-management.service.ts lines 347-356 (inline catch in updateSchema)
Compare with handleSchemaError at line 362 which correctly handles all error formats.
Context
Found during error handling audit in PR #31.
Problem
updateSchemainsrc/services/serverless-schema-management.service.tshas its own inline error handler (lines 347-356) that does not callhandleSchemaError. It usesJSON.stringify(error.response.data)instead of extracting the human-readable message.All other methods in this service correctly delegate to
handleSchemaError, which extractsdata.message,data.error, plain-text strings, etc.Expected behavior
updateSchemashould delegate tohandleSchemaErrorlike the other methods, so Cloud Serverless{"code":"...","message":"..."}errors are surfaced as readable messages instead of raw JSON blobs.Affected code
src/services/serverless-schema-management.service.tslines 347-356 (inline catch inupdateSchema)Compare with
handleSchemaErrorat line 362 which correctly handles all error formats.Context
Found during error handling audit in PR #31.