Apologies if I missed this somewhere. I’m migrating from version 2 -> 3. `ApolloSubscriptionCall....

# apollo-kotlin

[Chris Fillmore]

Apologies if I missed this somewhere. I’m migrating from version 2 -> 3. ApolloSubscriptionCall.Callback had onFailure and onTerminated. How are these exposed in Apollo 3.x?

Can I .catch?

subscriptionCall.toFlow()
  .catch { ... }
  .collect { ... }

[Chris Fillmore]

For that matter is onConnected behaviour still exposed?

[Stylianos Gakis]

Since it's now a flow, would the flow extensions like .onStart {} fit your use case?
Also yeah you can definitely use the .catch operator there for anything that may be thrown.

I'd guess this should have similar functionality to what old "onFailure" was, but I'd definitely read the docs about what old onFailure was.

[Chris Fillmore]

I haven’t checked recently but I thought onFailure mapped to OkHttp websocket listener’s equivalent callback

[Chris Fillmore]

Thanks for responding

[Chris Fillmore]

I haven’t yet used onStart, let me take a look