This repository was archived by the owner on May 29, 2025. It is now read-only.
Add SchemaValue.json extension for proper JSONSchema → JSON conversion #29
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Problem: MCPServer Schemable+extensions.swift failed to compile because its Input.schema.schemaValue does not have .json field. I added a SchemaValue.json extension that reuses the existing dictionary‐to‐JSON conversion logic and handles the boolean case, restoring correct schema serialization
Details
This change introduces a new json computed property on SchemaValue in Schemable+extensions.swift, enabling direct conversion of SchemaValue to the project’s JSON type. By delegating object-case conversion to the existing [KeywordIdentifier: JSONSchema_JSONValue].json extension (and ultimately to JSONSchema_JSONValue.value),
we:
With this in place, tools defined via @Schemable can correctly expose their input schema as JSON.