Skip to content

Conversation

@kpavlov
Copy link
Contributor

@kpavlov kpavlov commented Nov 12, 2025

  • Updated integration tests to include assertions for meta being null in the listTools, listResources, readResource, and callTool results.
  • Renamed test cases in SseServerIntegrationTest for clarity.
  • Added (deprecated) synthetic constructors for various request parameter classes.
  • Enhanced naming conventions and structure in integration test cases.
  • Replaced throw Error(...) with error(...) for cleaner error handling.

Motivation and Context

To verify backwards-compatibility after schema change

How Has This Been Tested?

CI, integration tests, regression tests (samples)

Breaking Changes

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update
  • Test update

Checklist

  • I have read the MCP Documentation
  • My code follows the repository's style guidelines
  • New and existing tests pass locally
  • I have added appropriate error handling
  • I have added or updated documentation as needed

Additional context

- Updated integration tests to include assertions for `meta` being `null` in the `listTools`, `listResources`, `readResource`, and `callTool` results.
- Renamed test cases in `SseServerIntegrationTest` for clarity.
@kpavlov kpavlov marked this pull request as ready for review November 12, 2025 11:25
@kpavlov kpavlov changed the title Add _meta/meta assertions for SDK client tests Add backwards compatibility constructors and tests Nov 12, 2025
…ity for paginated request parameters, and enhance `meta` handling across SDK components.
@kpavlov kpavlov added bugfix Something was fixed 🎉 refactoring Making things better labels Nov 12, 2025
@kpavlov kpavlov requested a review from devcrocod November 12, 2025 17:39
Copy link
Contributor

@devcrocod devcrocod left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I only have some comments about the code style

* The argument's information for which completion options are requested.
*/
public val argument: CompleteRequestParams.Argument
public val argument: Argument
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It’s better to refer to the class directly rather than importing it separately
this makes the code clearer and easier to understand:
CompleteRequestParams.Argument

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Idea complains about it but yes

* Additional, context for generating completions.
*/
public val context: CompleteRequestParams.Context?
public val context: Context?
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The same as with Argument

@kpavlov kpavlov merged commit 8bdbd36 into main Nov 12, 2025
7 checks passed
@kpavlov kpavlov deleted the kpavlov/tests_meta branch November 12, 2025 18:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bugfix Something was fixed 🎉 refactoring Making things better

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants