fix: update README and introspection logic to support schema files hosted at URLs #32
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:
This pull request introduces enhancements to the
mcp-graphqlproject, enabling support for GraphQL schema files hosted at URLs. The changes include updates to the README documentation and modifications to the introspection logic to accommodate schema files accessible via HTTP/HTTPS URLs.Changes Made:
README Updates:
SCHEMAenvironment variable can now accept a URL in addition to a local file path.Code Enhancements:
introspectSchemaFromUrlin introspection.ts to fetch and process schema files hosted at URLs.introspectLocalSchemafunction to ensure consistent formatting.SCHEMAvariable is a URL and uses the appropriate introspection method.Error Handling:
Testing:
Impact:
These changes enhance the flexibility of the
mcp-graphqlserver, allowing users to work with schema files hosted remotely, which is particularly useful for distributed environments or when schema files are managed externally.Issue Reference:
No specific issue linked.
Reviewer Notes:
Additional Context:
This update aligns with the project's goal of providing robust and flexible GraphQL tooling for diverse use cases.