Skip to content

update documentation for Transport.ConnContext #92

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jun 9, 2025

Conversation

marten-seemann
Copy link
Member

This was introduced by @sukunrt in quic-go/quic-go#5122 and released in v0.52.0.

@marten-seemann marten-seemann requested a review from Copilot June 9, 2025 10:39
Copilot

This comment was marked as outdated.

Copy link

@sukunrt sukunrt left a comment

Choose a reason for hiding this comment

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

whoops. missed this.

@marten-seemann marten-seemann requested a review from Copilot June 9, 2025 15:01
Copy link
Contributor

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This PR updates the documentation for Transport.ConnContext to reflect its new signature introduced in v0.52.0.

  • Updated the function signature in the code sample to include an additional parameter and return an error.
  • Added a callout section explaining how returning an error can reject a connection attempt.
Comments suppressed due to low confidence (1)

content/docs/quic/connection.md:21

  • [nitpick] Consider adding a brief inline comment to explain the purpose of the new 'info' parameter to improve clarity for readers of the documentation.
ConnContext: func(ctx context.Context, info *quic.ClientInfo) (context.Context, error) {

@marten-seemann marten-seemann merged commit 4b8d31d into master Jun 9, 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