docs: update server requirements #10
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
pcarleton
approved these changes
Nov 7, 2025
Member
pcarleton
left a comment
There was a problem hiding this comment.
LGTM, thanks for these adjustments.
I think it's likely in the future we'll want to find a way to generate this from the test code so we're not stuck manually updating it for every test change.
Contributor
Author
That's an interesting idea, not straightforward but definitely interesting, I'll see if I can come up with something |
Contributor
Author
|
@pcarleton I think you need to approve the workflow for the automerge to take place |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This PR fixes some mistake in the expected output of
SERVER_REQUIREMENTSwhile also updating the code blocks to bejsonrather thantypescript.Motivation and Context
everything-serverwhile following the guide was resulting in a few errors because, for example, the tests for elicitation don't actually response with a{ "respose": "" }object but with a{ username: "", email: "" }object. Also the test fortest_error_handlingcorrectly checks forisErrorandcontentin the response but the guide was still expecting an error to be thrown.;at the end of thecontentarray meaning copying them to paste them in the server will always require removing that semicolon to have proper syntax. Having them as JSON will allow to just copy paste them (and the formatter will remove the unnecessary quotes).How Has This Been Tested?
I have built an
everything-serverand verified the changes are correct.Breaking Changes
Nope.
Types of changes
Checklist