You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Opt-in output schema validation for tool calls. A new mocapi.tools.validate-output property (default false) installs an OutputSchemaValidatingInterceptor next to the existing input validator on every tool handler. When on, each tool's return value is validated against its derived output schema and a mismatch fails loudly with JSON-RPC -32603, surfacing schema/reality drift at test time instead of as an opaque gateway 500 in production. The interceptor switches on the result shape: CallToolResult validates structuredContent (skipped when null), JsonNode validates directly, null is skipped, anything else is serialized via valueToTree and validated. Flip it on in @SpringBootTest runs to catch drift before clients do.
Changed
mocapi-server tests aligned to draft_2020_12. Production has defaulted mocapi.tools.schema-version to draft_2020_12 for a while, but three mocapi-server tests were still instantiating DefaultMethodSchemaGenerator with SchemaVersion.DRAFT_7. Flipping them to match the production default is a correctness fix, not cosmetic — and it also cut mocapi-server's test-suite wall time from ~15.7s to ~5.7s.
Documentation
Removed two obsolete example ITs (PostgresqlStarterAutoConfigurationIT, RedisStarterAutoConfigurationIT) that spun up Testcontainers only to verify Substrate's own Postgres/Redis auto-configurations. They didn't exercise a single mocapi type and referred to mocapi-specific "starters" that no longer exist. Saves ~22s of Docker per CI run.