and they all remain compatible with Either

# arrow

[pakoito]

and they all remain compatible with Either

[Davide Giuseppe Farella]

Thank you, my intent is to have some kind of “sealed safety”, like what we can have with `sealed class`es like

sealed class Result {
  object Success : Result()
  object Failure : Result()
}

sealed NetworkError {
  object Success : NetworkResult()
  object NoNetwork : NetworkResult()
}

but with some kind of ereditariety

[pakoito]

yes, that SomeError is a sealed class, and so is NetworkError

[pakoito]

“Success” is the right side of every Either

[pakoito]

and you only have to fill the left side with errors

[pakoito]

and for that you create the sealed class hierarchy I’ve suggested

[Davide Giuseppe Farella]

But there are 2 problems there :)
1) can't extend the sealed in another file
2) if LoginError extend NetworkError, WrongCredentials is a network error, so it must be covered in a when (NetworkError), but viceversa a LoginError cannot be a NetworkError.NoNetwork

[Davide Giuseppe Farella]

I think I have to do

sealed class LoginError {
    object WrongCredentials : LoginError() 
    class Network(
        val reason: NetworkError
    ) : LoginError() 
}

Either is a good solution though

[dcampogiani]

https://www.youtube.com/watch?v=OuCVkBSBwBA&t=1038s▾

[dcampogiani]

minute 17

[dcampogiani]

abstract class FeatureFailure

[dcampogiani]

and he’s spanish so he must know about functional programming in kotlin

[Davide Giuseppe Farella]

Looks interesting, thank you! I'll try to play with it