fix(Validation): Make "mcp_config" optional when using uv #181
+122
−52
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.
Motivation and Context
Documentation states that the
mcp_serverconfig variable should not be necessary when usinguvas a server type.However, when attempting to compile a manifest without one, compilation failed with the following error message:
This was due to
mcp_configbeing enforced in the schema for all server types. This PR makesmcp_serveroptional when the server type is set touv.How Has This Been Tested?
This was tested locally by attempting to compile the following manifest.json:
Breaking Changes
No breaking changes.
Types of changes
Checklist