🤗 [Question]: Must Websocket Locals be read-only?

[supagroova]

Question Description

I notice that the Locals are read-only within the Websocket, and I was wonder if there is a reason for that?

I'm looking to persist user context through-out the length of the connection and was hoping to use Locals.

Would something like the below change be feasible? (I can submit a PR if so)

Code Snippet (optional)

// Locals makes it possible to pass interface{} values under string keys scoped to the request
// and therefore available to all following routes that match the request.
func (conn *Conn) Locals(key string, value ...interface{}) interface{} {
	if len(value) == 0 {
		return conn.locals[key]
	}
	conn.locals[key] = value[0]
	return value[0]
}

Checklist:

• I agree to follow Fiber's Code of Conduct.
• I have checked for existing issues that describe my questions prior to opening this one.
• I understand that improperly formatted questions may be closed without explanation.