Skip to content

Conversation

@iqdoctor
Copy link
Contributor

- Replace custom "sse/connection" notification with standard "notifications/message"
- Use params {level: "info", data: "SSE Connection established"} to match MCP logging schema
- Avoid pydantic validation errors for unexpected notification method/shape (issue punkpeye#33)
@punkpeye
Copy link
Owner

Looks like the checks are not passing.

- Send SSE connection notification as a spec-compliant `notifications/message` with {data, level} payload
- Order params keys as {data, level} to comply with eslint-perfectionist/sort-objects
@iqdoctor
Copy link
Contributor Author

iqdoctor commented Nov 16, 2025

Tnx. I simply swapped the order of the data and level keys, and all tests passed.

@punkpeye
Copy link
Owner

This is still failing just in case

@iqdoctor
Copy link
Contributor Author

pls apply if after #47

@punkpeye
Copy link
Owner

#47 merged

@iqdoctor
Copy link
Contributor Author

let me check test results

@iqdoctor
Copy link
Contributor Author

all passed

@iqdoctor
Copy link
Contributor Author

@punkpeye PR ready

@punkpeye punkpeye merged commit 0bb50c0 into punkpeye:main Nov 23, 2025
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants