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
MutableSharedFlow interface, in turn, says in its documentation that an instance can be created using this function.
SharedFlow relays on these parameters. However, they are not a part of the interfaces and are present only as parameters to the constructor function. They are part of the SharedFlowImpl class, which is internal in kotlinx.coroutines.core.
This makes it hard to properly serialize SharedFlows in the kotlinx.rpc library.
Can you, please, advise what can be done to improve this situation? We need a multiplatform approach to retrieve these parameters, however, we don't have one now
The text was updated successfully, but these errors were encountered:
Could you please elaborate on the lifecycle of such a SharedFlow? E.g. the particular use-case how and why it is serialized and what it represents to clients etc.
MutableSharedFlow function has three parameters:
MutableSharedFlow interface, in turn, says in its documentation that an instance can be created using this function.
SharedFlow relays on these parameters. However, they are not a part of the interfaces and are present only as parameters to the constructor function. They are part of the
SharedFlowImpl
class, which is internal in kotlinx.coroutines.core.This makes it hard to properly serialize SharedFlows in the kotlinx.rpc library.
Can you, please, advise what can be done to improve this situation? We need a multiplatform approach to retrieve these parameters, however, we don't have one now
The text was updated successfully, but these errors were encountered: