Fix parsing issues #10
Open
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.
Fix: Partial Parsing of
$refObjects and Schema Examples in Request BodyHi there 👋
I recently came across this project and gave it a try using the specs in the
example/directory. While testing, I noticed a few issues related to parsing and transformation to mcp tool spec. I've made some initial fixes, specifically targeting the request body section for now.✅ Changes Included
$refObject Parsing$refkey with its corresponding target object fromp.document.components.Unexpected Fields in Tool Spec Conversion
Schema
exampleParsingexamplefield defined underschema.Schemastruct to hold this data.Final output looks like this:
Let me know if this approach works for you. I'd be happy to help extend the fix to other parts if needed!
Thanks 🙌