You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Today, it's possible to use paramsProvider to send additional information during the channelAuthorization call. When using more and more different channels, this is starting to grow our payload significantly because the paramsProvider isn't aware of the channel being subscribed to and have to return the params for all possible options to the backend, and the backend can then look at the appropriate params depending on the channel being authorized, by looking at the channel_name parameter.
What is the expected behavior?
I think it would make our implementation quite easier if paramsProvider could be provided with the params argument at the moment it's called:
Do you want to request a feature or report a bug?
This would be a new feature request
What is the current behavior?
Today, it's possible to use
paramsProvider
to send additional information during the channelAuthorization call. When using more and more different channels, this is starting to grow our payload significantly because theparamsProvider
isn't aware of the channel being subscribed to and have to return the params for all possible options to the backend, and the backend can then look at the appropriate params depending on the channel being authorized, by looking at thechannel_name
parameter.What is the expected behavior?
I think it would make our implementation quite easier if
paramsProvider
could be provided with theparams
argument at the moment it's called:pusher-js/src/core/auth/channel_authorizer.ts
Line 28 in ed900f8
Which versions of Pusher, and which browsers / OS are affected by this issue?
Did this work in previous versions of Pusher? If so, which?
Using pusher 8.3.0, same behavior on current master
The text was updated successfully, but these errors were encountered: