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
I have to implement support for multichannels in Next's CKO integration. Developers will be able to pick up channel. That's why they will have to use some setChannel method in proper moment in their app.
Ofc, with some fallback to previous value if someone tries to use a non existing channel.
The function will be exported in index.ts so we should be able to import it with:
I think it's another function in useCko composable that allows you to change channel, @Fifciu is there any concern why that's a bad idea? The composables shouldn't know about where parameters (URL etc.) comes from, you provide this from the app
I have to implement support for multichannels in Next's CKO integration. Developers will be able to pick up channel. That's why they will have to use some
setChannel
method in proper moment in their app.The current shape of the config:
The proposed shape of the new config:
I would export function called
setChannel
which would take one argument -channelKey: string
. It would be something like:Ofc, with some fallback to previous value if someone tries to use a non existing channel.
The function will be exported in index.ts so we should be able to import it with:
What do you think about this approach?
The text was updated successfully, but these errors were encountered: