@VoyTechnology I just wanted to ask a question.Currently the demand of this issue is just to make the existing functions support context or should we have to change functions so that every functions just needs the context parameter and all the data to be used in the function body will be extracted from the context body itself?

@partik03 I am not sure I fully understand your question so I will try and answer based on my interpretation:

We would pass in a new context.Context argument at the beginning of every function. thing string, data any will remain unmodified. How the context will be used after being passed into the function is outside the scope of this feature request, but it is safe to assume it can be used to handle tracing, request cancellation, log context etc., but the actual data that will be sent will still be part of the data any parameter.

@VoyTechnology got it.Thanks!

@VoyTechnology can I take up this one?

@VoyTechnology As the project uses gorilla for making websocket connections and gorilla does not have a single context variable as you mentioned above so should I use the standard http request and response variables or should I include a library like gofiber which takes care of the context in a single variable?

Hey @VoyTechnology @partik03 !

We do intend to standardise the interface, which would include the addition of context.Context.

If you @partik03 or someone else would like to add it to the existing API then we would definitely merge that. But just giving a heads up that it is likely to change in the future.