Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Add ReadLimit to Option structs

Open
#244 9 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
38/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
go

Research direction

Start by locating the AcceptOptions and DialOptions definitions and the SetReadLimit method, then trace how each option creates a connection. Determine how a zero-valued field should interact with the default limit and whether the method must remain usable for dynamic changes. Done means both option structs can configure the initial read limit without removing the existing method behavior.

Written by the indexing model from the issue text.

Description

enhancement

Would it be possible to add a field to AcceptOptions and to DialOptions that sets the read limit on the created connection? It's not as convenient to have to call the SetReadLimit(). If the field is 0 then a default limit can be applied.

Is there a need to change the limit dynamically? I mean, why is it a method (i.e. can be called multiple times) vs a field in those option setting structs?

Dominant language
Go
Stars
5.5k
Forks
377
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from coder/websocket

All issues in coder/websocket

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.