-
Couldn't load subscription status.
- Fork 551
Overhaul of Resources #125
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Overhaul of Resources #125
Conversation
- Introducing separate classes for Text and Blob ResourceContents - Custom JSON converter to allow those types to be returned, making it easier to follow the type system against the spec - Updated tests
src/ModelContextProtocol/Protocol/Types/Resources/BlobResourceContents.cs
Outdated
Show resolved
Hide resolved
src/ModelContextProtocol/Protocol/Types/Resources/ResourceContents.cs
Outdated
Show resolved
Hide resolved
src/ModelContextProtocol/Protocol/Types/Resources/ResourceContents.cs
Outdated
Show resolved
Hide resolved
src/ModelContextProtocol/Protocol/Types/Resources/TextResourceContents.cs
Outdated
Show resolved
Hide resolved
Co-authored-by: Stephen Toub <[email protected]> Co-authored-by: Peder Holdgaard Pedersen <[email protected]>
src/ModelContextProtocol/Protocol/Types/BlobResourceContents.cs
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Once the remaining comments are addressed, LGTM. Thanks!
Co-authored-by: Stephen Toub <[email protected]>
Fixed that one and I think I got the merge correct from your change (and I fixed that at the same time) |
This is an update to the Resources and ResourceTemplates part of the MCP server which aims to align the data structures more with the structure that we see in the spec (using 2024-11-05 as the spec target).
WithReadResourceHandlershould work if you only provideWithListResourceTemplatesHandler#123 by allowing a ListResourceTemplates handler to work in conjunction with ReadResourcesRequestRather than using
ResourceContentsas a combination of the properties across blob and text resources, I've turned this into an abstract class and have implementations of the types. This more closely aligns with the structure we see in the schema, making it easier to map our types to the source types.