Chore/rename request context #54
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What changed?
Renamed
RequestContexttoMessageContextacross both client and server sides. This includes updating the class names, file names (request_context.py→message_context.py), all imports, type signatures, and test references.Closes #44
Why?
The original name
RequestContextwas misleading since the context is used for both requests AND notifications. The class contains general client/server state and communication helpers, not request-specific data.Impact
Testing
Review notes
This is a pure rename with no logic changes. The context object provides the same functionality, just with a name that accurately describes its purpose across all message types.
Checklist